Skip to main content Skip to complementary content

Microsoft SQL server

MSSQL connectors are used to connect to Microsoft SQL server reports.

Connection string: The connection string to your SQL Database.

Connector Server Aliases: Used to fully inform Qlik Lineage Connectors of the different ways of referring to the data source.

Test: Performs a control of the connection string and verifies the ability to connect to SQL.

Microsoft SQL Server rules

Extract Tables: When enabled, Qlik Lineage Connectors gather tables and fields definitions from the system table, together with some metadata surrounding them.

Extract Views: When enabled, Qlik Lineage Connectors go through the defined views in the database, and parses the definitions.

  • Create view dependencies: If enabled, Qlik Lineage Connectors analyze the SQL statements in the view definitions and generates lineage on field level to other database entities.

Extract Procedures: When enabled, Qlik Lineage Connectors go through the defined procedures in the database, and parses the definitions.

  • Create procedure dependencies: If enabled, Qlik Lineage Connectors analyzes the SQL statements in the procedure definitions and generates lineage on field level to other database entities.

Extract Functions: When enabled, Qlik Lineage Connectors go through the defined functions in the database, and parses the definitions.

  • Create function dependencies: If enabled, Qlik Lineage Connectors analyze the SQL statements in the function definitions and generates lineage on field level to other database entities.

Include Databases: A semicolon separated list of databases to act upon with the above ruleset. Does not support wildcard.

Schema Filter: The schema filter is used to decide what schemas to include. For example, you could use the definition *.dbo.* ; AdventureWorks.Sales.* to gather all tables from the dbo schema of all your databases, but also the tables from the Sales schema on the AdventureWorks catalog.

Folder Alias

A folder alias will synchronize the different references that a connector may read from. For example, an application may refer to a folder as \\mssql01-prod\sources but in a script it is referred to as \\mssql01-prod.company.com\sources. In this case, the two different references point to the same folder, but it will not appear like that in the lineage graphs. By adding the alias, the resource name will be synchronized, and the graphs will reconcile.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!