Microsoft Azure SQL Database lineage configuration

Include and exclude lists

You can include or exclude assets up to the schema level. Provide databases and schemas in the format database/schema. Each part is evaluated as a regular expression. Assets which are added later in the data source will also be included or excluded if they match the conditions specified in the lists. Example values:

• myDB/: all schemas in myDB database.
• myDB2/.*: all schemas in myDB2 database.
• myDB3/mySchema1: mySchema1 schema from myDB3 database.
• myDB4/mySchema[1-5]: any schema in my myDB4 database with a name that starts with mySchema and ends with a digit between 1 and 5.

External inputs

If you use external SQL and T-SQL scripts for Microsoft Azure SQL Database, you can add them in a .zip file as an external input. You can organize the structure of a .zip file as subfolders that represent databases and schemas. After the scripts are scanned, they are added under respective databases and schemas in the selected catalog or project. The .zip file can have the following structure:

    <database_name>
        <schema_name>
           <script_name.sql>
    <database_name>
        <script_name.sql>
    <script_name.sql>
    replace.csv
    linkedServerConnectionsConfiguration.prm

The replace.csv file contains placeholder replacements for the scripts that are added in the .zip file. For more information about the format, see Placeholder replacements.

The linkedServerConnectionsConfiguration.prm file contains linked server connection definitions. The following structure defines a single connection:

[{Shortcut_Name}] Type={connection_type}
Connection_String={connection_string}
Server_Name={server_name}
Database_Name={database_name}
Schema_Name={schema_name}
User_Name={user_name}

Advanced import options

Extract extended attributes

You can extract extended attributes like primary key, unique and referential integrity constraints of columns. By default these attributes are not extracted.

Extraction mode

You can decide which extraction mode to run for the imported metadata. You have the following options:

• Prefetch: use it for relational databases.
• Parallel bulk: use it for analytical processing engines.
• Single-thread: use it to avoid parallelism and large queries during extraction. When you select this mode, performance might be low.

Transformation logic extraction

You can enable building transformation logic descriptions from SQL code in SQL scripts.