Configure the synchronization of a data source

After you registered your data source via Edge, you configure the synchronization of your data source by means of table rules to determine which schemas and tables are ingested and how they are ingested. After this, you can synchronize them.

Prerequisites

• You have a global role with the Catalog global permission, for example Catalog Author.
• You have a resource role with the Configure external system resource permission, for example Owner.
• You have a global role with the View Edge connections and capabilities global permission.
• You have registered your database via Edge.

Steps

1. Open a Database asset page.
2. In the tab pane, click Configuration.
3. In the Metadata extraction tab page, select a schema.
   Tip 

   • You can search for a schema in the drop-down list or use the filter to show only schemas with or without table rules.
   • You can refresh the schema list, by clicking the Refresh List icon.
4. If required, create or edit the table rule:
   1. Perform one of the following steps:
      
      • To create a new table rule, click Add table rule.
      • To edit an existing table rule, click Edit in the upper right corner.
   2. Enter the required information.

      Table rule field	Description
      Include	A comma-separated list of the names of the tables you want to synchronize. In the list, add a space after each comma. For example, CUSTOMERS, ORDER, SKU. You can use * as a wildcard. The default value is *, which means all tables are taken into account. The Include field takes priority over the Exclude field. Example  Out of all tables in a schema, you only want to synchronize the table with name "CUSTOMERS" and the tables with a name that starts with "ORDER". To do this: In the Include field, enter: CUSTOMERS, ORDER*. Out of all tables in a schema, you only want to synchronize the tables with a name that contains "SKU". To do this: In the Include field, enter: *SKU*.
      Exclude	A comma-separated list of the names of the tables you do not want to synchronize. In the list, add a space after each comma. For example, CUSTOMERS, ORDER, SKU. You can use * as a wildcard. The Include field takes priority over the Exclude field. You can use the Exclude table rule to do the following: Synchronize all tables in a schema except the ones defined in the Exclude field. Synchronize only tables as defined in the Include field, with the exception of tables that are listed in the Exclude field. Example  Out of all tables in a schema, you do not want to synchronize a table with the name "ADDRESS" and tables with a name that ends with "PHONE". To do this: In the Include field, enter: * and in the Exclude field, enter: ADDRESS, *PHONE. Out of all tables in a schema, you want to synchronize the tables with a name that starts with "SKU", but exclude the tables with a name that contains "bkp". To do this: In the Include field, enter: SKU* and in the Exclude field, enter: *bkp*. From the following list, only "SKU_1" and "SKU_2" will be synchronized. SKU_1 , SKU_2, SKU_bkp_1, SKU_bkp_2, New, bkp, bkp_SKU
      Target domain	The Physical Data Dictionary domain in which the schema is synchronized. The default value is Schema domain: the metadata is placed in a domain located in the same community as the domain of your Database asset. If that domain doesn't exist yet, Data Catalog creates it. You can select any other Physical Data Dictionary domain for which you have a resource role with the Configure external system resource permission.
      Options	Additional options to specify which type of tables you want to synchronize.
      Skip database views	A checkbox to exclude database views from the synchronization process. If selected, no assets of the type Database view are created. Tip You can also use the table rules to include or exclude specific database views.

   3. Click Save.
      A table icon () appears next to the schema name in the schema list.
5. If required, delete a table rule:
   1. Click Edit in the upper right corner.
   2. In the upper-right corner, click → Delete.

Note You can only synchronize schemas that have table rules.

What's next?

You can now synchronize the schemas to ingest the metadata into Collibra.