Step 2. Configure capabilities

When you configure the Microsoft Azure Synapse Data Warehouse Script catalog source, you define the settings for the metadata extraction capability and other optional capabilities.

The metadata extraction capability extracts source metadata from external source systems. You can also configure other capabilities that the catalog source includes.

You can save the catalog source configuration at any point after you enter the connection information. After you save the catalog source, you can choose to run the catalog source job. To run the job once, click Run. To run metadata extraction and other capabilities on a recurring schedule, configure schedules on the Schedule tab.

Configure metadata extraction

When you configure the Microsoft Azure Synapse Data Warehouse Script catalog source, you choose a runtime environment, define filters, and enter configuration parameters for metadata extraction.

1In the Connection and Runtime area, choose a serverless runtime environment or the Secure Agent group where you want to run catalog source jobs.

Note:

Serverless runtime environment options are available if the catalog source works with a serverless runtime environment.

2Choose to retain, delete, or deprecate objects that are deleted from the source system in the catalog with the Metadata Change Option.

- Retain. Retains objects that are deleted from the source system in the catalog. If you update or add a filter, the catalog retains objects extracted from the previous job and extracts additional objects that match the current filter. Objects deleted from the source system are not deleted from the catalog. Enrichments added on deleted objects and relationships are retained.
- Delete. Deletes metadata from the catalog based on objects deleted from the source system and changes you make to the filter. Enrichments added on deleted objects and relationships are also permanently lost. Objects renamed in the source system are removed and recreated in the catalog.
- Deprecate. The lifecycle of objects imported into the catalog moves to Obsolete based on objects deleted from the source system and changes you make to the filter. This does not impact enrichments added on deprecated objects and relationships. Objects renamed in the source system are removed and recreated in the catalog. When you run the catalog source job again for other capabilities such as data classification, relationship discovery, or glossary association, the job doesn't consider obsolete objects. Obsolete objects remain in the catalog until they are purged when you run a Purge Obsolete Objects job on the Explore page.

Note:

You can also change the configured metadata change option when you run a catalog source.

3In the Filters area, define one or more filter conditions to extract metadata:

aSelect Yes to view filter options.
bFrom the Include/Exclude list, choose to include or exclude metadata based on the filter parameters.
cFrom the object type list, select Script Path.
dEnter the script path as the filter value.

Filter values can contain wildcards. Use the following rules when you enter filter values with wildcards:

▪ Use an asterisk to represent multiple characters.
▪ Use a question mark to represent a single character.
▪ If an object contains an asterisk or a question mark, enclose the symbol in double quotes.
▪ If a filter value contains spaces before or after the string value, enclose the value in double quotes.
▪ Don't use wildcards in file paths. To enter a path hierarchy, use separators, such as a period or a slash, which the source system allows.

The following image shows the filter condition: The image shows the filter conditions for the Microsoft Azure Synapse Data Warehouse Script catalog source. You can choose to include or exclude metadata from specific script paths.

The image shows the filter conditions for the Microsoft Azure Synapse Data Warehouse Script catalog source. You can choose to include or exclude metadata from specific script paths.

If the scripts root directory path is /users/opt/input, use the following examples to create filter conditions:

▪ To include or exclude metadata from the script named script1.sql located in the path /users/opt/input/folder1/, enter: folder1/script1.sql
▪ To include or exclude metadata from all scripts with SQL extension stored in the path /users/opt/input/folder1/, enter: folder1/*.sql
▪ To include or exclude metadata from all scripts stored in the path /users/opt/input/, enter: *
▪ To include or exclude metadata from all scripts with SQL extension and names that start with 'script' followed by a single character, stored in the path /users/opt/input/folder1/, enter: folder1/script?.sql

eOptionally, to define an additional filter with an OR condition, click the Add icon.

4In the Configuration Parameters area, enter configuration parameters.

The following table describes the properties that you can enter:

Property	Description
Scripts Root Directory Path	Path to the remote SQL script root directory.
Default Database	Default database for the SQL script processing.
Default Schema	Default schema for the SQL script processing.
MetaTables Include Filter	Advanced parameter. When you process PL/SQL statements, Metadata Command Center does not read tables or view content by default. If you want to use the content, for example, to process dynamic SQL statements, use the MetaTables Include Filter parameter. This parameter prompts the database for the required metadata. Verify that the user has SELECT permissions for metatables. Note: This parameter appears when you click Show Advanced . Note: Don't use this option to specify filters for tables that you want to include or exclude during the metadata extraction run.
Additional Settings	Configure expert parameters to specify additional configuration options to be passed at runtime. Required if you need to troubleshoot the catalog source job. Caution: Use expert parameters when it is recommended by Informatica Global Customer Support. Note: This parameter appears when you click Show Advanced .

5Configure additional capabilities for the catalog source by clicking on the tabs.

Configure lineage discovery

Enable the lineage discovery capability and use CLAIRE to build complete lineage by recommending endpoint catalog source objects to assign to reference catalog source connections.

1Click the Lineage Discovery tab.

2Select Enable Lineage Discovery.

3In the Filters area, define one or more filter conditions to apply for lineage discovery.

To define filters, you can choose to select catalog source types, asset groups, or enter a catalog source name or search from a list of catalog sources.

aSelect Yes to view filter options.
bFrom the Include/Exclude list, choose to include or exclude catalog sources for lineage discovery based on the filter parameters.
cFrom the filter type list, select catalog source type, catalog source name, or asset group.
dIn the filter value field, select the required catalog source types, or click the Search button and select catalog sources or asset groups.

Filters can contain the asterisk wildcard to represent multiple characters or empty text.

The filter options appear. The filter options include multiple filter conditions that you can choose.

Examples:

▪ To include or exclude all Oracle catalog sources, select Catalog Source Type as the filter type and select Oracle in the filter value field.
▪ To include or exclude the 'Oracle_Retail' catalog source, select Catalog Source Name as the filter type and search for the catalog source or enter Oracle_Retail in the filter value field.
▪ To include or exclude all catalog sources with names that start with 'Oracle', select Catalog Source Name as the filter type and search for the catalog source or enter Oracle* in the filter value field.
▪ To include or exclude all catalog sources with names that end with 'Retail', select Catalog Source Name as the filter type and search for the catalog source or enter *Retail in the filter value field.
▪ To include or exclude all catalog sources with names that contain 'Ret', select Catalog Source Name as the filter type and search for the catalog source or enter *Ret* in the filter value field.
▪ To include or exclude all catalog sources that are part of the 'Financial Group' asset group, select Asset Group as the filter type and search Financial Group in the filter value field.

Note:

You can't add more than one include or exclude filter for the same filter type.

eOptionally, to define an additional filter with an AND condition, click the Add icon.

For more information about lineage discovery, see Lineage discovery.