Prepare a SQL Server Reporting Services <source ID> configuration file

The lineage harvester uses the lineage harvester configuration file to collect the SQL Server Reporting Services data objects and sends them to the Collibra Data Lineage server. However, if the useCollibrasystemName in the lineage harvester configuration file is set to true, you also have to provide a specific <source ID> configuration file that defines the system name of databases in SQL Server Reporting Services. This is necessary to enable the Collibra Data Lineage server to process multiple databases with the same name.

The SQL Server Reporting Services <source ID> configuration file can also be used to provide additional information about databases in SQL Server Reporting Services which is necessary if the databases do not contain all information to process the SQL source code correctly.

Prerequisites

Steps

  1. Create a new JSON file in the lineage harvester config folder.
  2. Give the JSON file the same name as the value of the Id property in the lineage harvester configuration file.
    Example The value of the Id property in the lineage harvester configuration file is ssrs-source-1. As a result, the name of your JSON file should be ssrs-source-1.conf.
  3. For each database in SQL Server Reporting Services, add the following content to the JSON file:

    Property

    		Description

    Required?

    DataSources

    This section contains all SQL Server Reporting Services connections for which you want to create a technical lineage.

    The DataSources section refers to shared data sources in SQL Server Reporting Services. For more information about shared data sources, see the Microsoft documentation.

    Yes

    <data source type>

    The name of a connection object in SQL Server Reporting Services.

    Yes

    dbname
    		The name of the database of a supported data source in SQL Server Reporting Services.

    No

    schema

    The name of the default schema of a supported data source in SQL Server Reporting Services.

    No

    dialect

    The dialect of the supported data source in SQL Server Reporting Services.

    No

    collibraSystemName

    The system or server name of the database.

    Yes

    CustomDataSources

    You can use custom data processing extensions that are used to support embedded data sources of which the data source definition is specified locally in a report or embedded data set.

    The CustomDataSources section refers to embedded data sources in SQL Server Reporting Services. For more information about embedded data sources, see the Microsoft documentation.

    No

    <path to report>/<custom data source name>

    The full path to the report and the custom data source name.

    You can use wildcards to match multiple folders, reports or data sets. The connection information is this section is used to add missing information or to overwrite parsed information.

    No

    dbname
    		The name of the database of a custom data source in SQL Server Reporting Services.

    No

    schema

    The name of the schema of a custom data source in power. If you don't provide the schema name, the default schema is used.

    No

    dialect

    The dialect of the custom data source in SQL Server Reporting Services.

    • azure, for an Azure SQL Server data source.
    • bigquery, for a Google BigQuery data source.
    • db2, for an IBM DB2 data source.
    • hana, for a SAP Hana data source.
    • hive, for a HiveQL data source.
    • greenplum, for a Greenplum data source.
    • mssql, for a Microsoft SQL Server data source.
    • mysql, for a MySQL data source.
    • netezza, for a Netezza data source.
    • oracle, for an Oracle data source.
    • postgres, for a PostgreSQL data source.
    • redshift, for an Amazon Redshift data source.
    • snowflake, for a Snowflake data source.
    • spark, for a Spark SQL data source.
    • sybase, for a Sybase data source.
    • teradata, for a Teradata data source.

    No

    .

    Copy code

    {
	"DataSources": {
		"Redshift": {
			"dbname": "redshift-database-name",
			"schema": "redshift-schema-name",
			"dialect": "redshift",
			"collibraSystemName": "redshift-system-name"
		},
		"Oracle": {
			"dbname": "oracle-database-name",
			"schema": "oracle-schema-name",
			"dialect": "oracle",
			"collibraSystemName": "oracle-system-name"
		}
	},
	"CustomDataSources": 
		"/path to report/custom data souce name": {
			"dbname": "mssql-database-name",
			"dialect": "mssql"
		}
	}
}

    Tip Click Copy code to copy the example to your clipboard.

  4. Save the <source ID> configuration file.