Register data source

The first step in using Data Notebook is to register a data source, which means creating a link between your Edge data source and Data Notebook. Data Notebook reuses Edge connections.

When registering a data source, you are prompted to choose how you want users to connect to the data source when they run queries, and where you want the query results for the data source to be stored. After you register a data source, you can't edit it.

Prerequisites

• You have a global role with the following global permissions:
  • Product Rights → Data Notebook
  • Data Notebook → Manage data sources
• If you want the query results to be stored in your organization's database, set up a database.
• To know the supported drivers for the data source, go to Data sources.

Steps

1. On the Data Notebook landing page, click Settings. Alternatively, on the main toolbar, click → Settings, and then, in the Data Notebook section, click Data sources.
2. On the Data Sources page, click Register data source.
   
3. In the Register a Data Source dialog box, enter the required information.
   

   Field	Description
   Edge site	This field contains a list of healthy Edge or Collibra Cloud sites.
   Data source connection	This field contains a list of supported connections associated with the Edge or Collibra Cloud site you selected.

4. Click Continue.
   
5. In the Choose the Authentication Method dialog box, select one of the following authentication options. These options vary by data source.

   Option	Description
   Service account	Users don't need to enter any credentials to connect to the data source, before running queries. Data Notebook will use the service account from the Edge data source connection.
   Personal credentials (applicable to Microsoft SQL Server, Oracle, PostgreSQL, Redshift, Teradata)	Users need to enter their own credentials, before running queries. They inherit permissions from the data source. When you select this option, the Credentials expiration field appears. By default, personal credentials expire after 1 month, but you can change the duration.
   Access keys (applicable to Amazon Athena)	Users need to enter their access keys, before running queries. They inherit permissions from the data source. When you select this option, the Credentials expiration field appears. By default, personal credentials expire after 1 month, but you can change the duration.
   Temporary security credentials (applicable to Amazon Athena)	Users need to enter their temporary security credentials, before running queries. They inherit permissions from the data source. When you select this option, the Credentials expiration field appears. By default, personal credentials expire after 1 hour, but you can change the duration.
   Google OAuth (applicable to BigQuery)	Users are redirected to Google for authentication, before running queries. They inherit permissions from the projects. This option requires you to create a Google OAuth application and obtain the client ID and client secret for such an application. To create this application, you need specific permissions on your Google Cloud console or need help from someone with those permissions. For more information, go to Google documentation.
   Personal access token (applicable to Databricks)	Users need to enter their personal access token that is generated on the Databricks platform, before running queries. For more information, go to Databricks personal access token authentication. When you select this option, the Credentials expiration field appears. By default, personal access token expires after 1 month. You can, however, change the duration.
   Microsoft Entra ID OAuth (applicable to Databricks and Snowflake)	Users are redirected to Microsoft Entra for authentication, before running queries. For more information, go to Register an application with the Microsoft identity platform. For Databricks: This option requires you to create a new Microsoft Entra ID application from the Azure portal and obtain the directory (tenant) ID, application client ID, and application client secret for the setup. For Snowflake: This option requires you to create a new OAuth server application from the Azure portal and obtain the Azure tenant ID and OAuth application ID URI. You also need to create a new OAuth client application from the Azure portal and obtain the OAuth client ID and OAuth client secret for the setup.
   Snowflake OAuth (applicable to Snowflake)	Users are redirected to Snowflake for authentication, before running queries. They inherit permissions from the data source. This option requires you to have the ACCOUNTADMIN role or a role with the CREATE INTEGRATION privilege in Snowflake to create and manage integrations for OAuth. You need to create an OAuth security integration and obtain the client ID and client secret for the setup.

6. Click Continue.
   
   Tip If you are registering Snowflake, the Set up Snowflake OAuth dialog box appears first. Follow the instructions, click Continue, enter the OAuth Client ID and OAuth Client Secret, and then click Continue again.
7. In the Link your data source to the Collibra Catalog dialog box, select one of the following options to link your data source to a System asset in Data Catalog.

   Option	Description
   Use Edge connection name	Allows Collibra to use the name of the Edge connection to link to a related System asset of the same name in Data Catalog.
   Specify a system in Catalog	Allows you to select an existing System asset that represents your data source in Data Catalog. Use this option if the name of the Edge connection doesn't match the name of the System asset in Data Catalog.

8. Click Continue.
   
9. In the Choose your data storage option dialog box, select one of the following storage options.
   

   Option	Description
   Store in Collibra Cloud	Stores the query results in Collibra Platform.
   Store in your own database	Stores the query results in your organization's database. For more information, go to Set up database for storing query results.
   Do not store results	Does not store the query results. The results are shown in the user's web browser until their browser is refreshed. They need to run the query each time they want to view the results. Even the asset created when publishing the notebook does not show the query results.

10. Click Continue.
    A message stating that the data source is registered appears.

What's next

Create a notebook.