Microsoft SQL Server Reporting Services (SSRS) (File) - Import - 7.1

Talend Data Catalog Bridges

English (United States)
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
Talend Data Catalog

Bridge Specifications

Vendor Microsoft
Tool Name SQL Server Reporting Services (SSRS)
Tool Version 9.0 (2005) to 14.x (2017)
Tool Web Site
Supported Methodology [Business Intelligence] ROLAP, BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure) via RDL XML File
Data Profiling
Remote Repository Browsing for Model Selection
Incremental Harvesting
Multi-Model Harvesting

Tool: Microsoft / SQL Server Reporting Services (SSRS) version 9.0 (2005) to 14.x (2017) via RDL XML File
Metadata: [Business Intelligence] ROLAP, BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure)
Component: MicrosoftSqlServerRs version 11.0.0

The bridge imports an SSRS Report from a file.



Refer to the current general known limitations at or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

Provide a trouble shooting package with:
- the debug log (can be set in the UI or in conf/ with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with option -backup)

In order to provide a complete set of source metadata to reproduce the issue, please export and attach the Report (RDL) files.

Bridge Parameters

Parameter Name Description Type Values Default Scope
RS File Specify here the Report file path to import. FILE
AS File Specify here an Analysis Service database file path. This parameter is useful if the selected report is based on an AS database.
Allows connecting the report to the source AS database. Otherwise, this parameter should be left empty.
Miscellaneous INTRODUCTION
Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g.
-connection.cast MyDatabase1="SQL Server"
Some options can be used multiple times if applicable, e.g.
-connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2;
As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g.

-java.memory <Java Memory's maximum size> (previously -m)

1G by default on 64bits JRE or as set in conf/, e.g.
-java.memory 8G
-java.memory 8000M

-java.parameters <Java Runtime Environment command line options> (previously -j)

This option must be the last one in the Miscellaneous parameter as all the text after -java.parameters is passed "as is" to the JRE, e.g.
-java.parameters -Dname=value -Xms1G
The following option must be set when a proxy is used to access internet (this is critical to access (and exceptionally a few other tool sites) in order to download the necessary third party software libraries.
-java.parameters -Dhttp.proxyHost= -Dhttp.proxyPort=3128 -Dhttps.proxyHost= -Dhttps.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass -Dhttps.proxyUser=user -Dhttps.proxyPassword=pass

-java.executable <Java Runtime Environment full path name> (previously -jre)

It can be an absolute path to javaw.exe on Windows or a link/script path on Linux, e.g.
-java.executable "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"

-environment.variable <name>=<value> (previously -v)

None by default, e.g.
-environment.variable var2="value2 with spaces"


Override the model name, e.g. "My Model Name"

-prescript <script name>

The script must be located in the bin directory, and have .bat or .sh extension.
The script path must not include any parent directory symbol (..).
The script should return exit code 0 to indicate success, or another value to indicate failure.
For example:
-prescript "script.bat arg1 arg2"


Clears the cache before the import, and therefore will run a full import without incremental harvesting.
Warning: this is a system option managed by the application calling the bridge and should not be set by users.

-backup <directory>

Full path of an empty directory to save the metadata input files for further troubleshooting.

Data Connections are produced by the import bridges typically from ETL/DI and BI tools to refer to the source and target data stores they use. These data connections are then used by metadata management tools to connect them (metadata stitching) to their actual data stores (e.g. databases, file system, etc.) in order to produce the full end to end data flow lineage and impact analysis. The name of each data connection is unique by import model. The data connection names used within DI/BI design tools are used when possible, otherwise connection names are generated to be short but meaningful such as the database / schema name, the file system path, or Uniform Resource Identifier (URI). The following options allows to manipulate connections. These options replaces the legacy options -c, -cd, and -cs.

-connection.cast ConnectionName=ConnectionType

Casts a generic database connection (e.g. ODBC/JDBC) to a precise database type (e.g. ORACLE) for SQL Parsing, e.g.
-connection.cast "My Database"="SQL SERVER".
The list of supported data store connection types includes:

-connection.rename OldConnection=NewConnection

Renames an existing connection to a new name, e.g.
-connection.rename OldConnectionName=NewConnectionName
Multiple existing database connections can be renamed and merged into one new database connection, e.g.
-connection.rename MySchema1=MyDatabase -connection.rename MySchema2=MyDatabase

-connection.split oldConnection.Schema1=newConnection

Splits a database connection into one or multiple database connections.
A single database connection can be split into one connection per schema, e.g.
-connection.split MyDatabase
All database connections can be split into one connection per schema, e.g.
-connection.split *
A database connection can be explicitly split creating a new database connection by appending a schema name to a database, e.g.
-connection.split MyDatabase.schema1=MySchema1 DestinationPath=SourcePath

Maps a source path to destination path. This is useful for file system connections when different paths points to the same object (directory or file).
On Hadoop, a process can write into a CSV file specified with the HDFS full path, but another process reads from a HIVE table implemented (external) by the same file specified using a relative path with default file name and extension, e.g. hdfs://host:8020/users/user1/folder/file.csv=/user1/folder
On Linux, a given directory (or file) like /data can be referred to by multiple symbolic links like /users/john and /users/paul, e.g. /users/John=/data /users/paul=/data
On Windows, a given directory like C:\data can be referred to by multiple network drives like M: and N:, e.g. M:\=C:\data N:\=C:\data

-connection.casesensitive ConnectionName

Overrides the default case insensitive matching rules for the object identifiers inside the specified connection, provided the detected type of the data store by itself supports this configuration (e.g. Microsoft SQL Server, MySql etc.), e.g.
-connection.casesensitive "My Database"


Bridge Mapping

Meta Integration Repository (MIR)
(based on the OMG CWM standard)
"Microsoft SQL Server Reporting Services (SSRS) (File)"
Mapping Comments
Attribute Table Field  
DesignLevel Logical Physical  
Name Name  
NativeType Column  
PhysicalName Name  
BaseType Database Field Datatype  
Name   Derived from the datatype
PhysicalName   Derived from the datatype
Class Database Table  
CppClassType   Set to ENTITY
CppPersistent   Set to True
DesignLevel Logical Physical  
Name Name  
NativeType Table  
ClassifierMap DataSet  
Name name  
Cube OLAPCube  
CubeDimensionAssociation OLAPCubeDimension  
DataAttribute SQL/MDX Item  
Name name  
Position position  
DataSet SQL/MDX Query  
Name name  
DatabaseSchema Database Schema  
DesignLevel Logical Physical  
Name Name  
NativeType Schema  
Stereotype Source  
DerivedType Database Field Datatype Report Field Datatype  
DataType Datatype  
Length length  
Name   Derived from the datatype
PhysicalName   Derived from the datatype
DesignPackage Report Data/Report Design and for each database catalog  
Name Name  
NativeType Logical Physical  
UserDefined False  
Dimension OLAP Dimension  
Description Description  
Name Name  
DimensionAttribute OLAPDimension Attribute  
Name Name  
FeatureMap   FeatureMap objects are used to hold the lineage of QueryItems DataAttributes, ReportDataAttributes
Operation expression text  
Hierarchy OLAPHierarchy  
Name Name  
HierarchyLevelAssociation OLAPHierarchyLevel  
Name Name  
Level OLAPLevel  
Name Name  
LevelAssociation OLAPHierarchyAssociation  
Name Name  
LevelAttribute OLAPLevel Attribute  
Name Name  
Measure OLAP Measure  
Description Description  
Name Name  
Encoding UTF-8  
ToolVersion 9.0 (2005) to 10.0 (2008  
VendorName Microsoft  
OlapSchema OLAP DataBase  
DesignLevel Logical Physical  
Name Name  
Report Report  
Description Description  
Name Name  
ReportAttribute ReportField  
DesignLevel Logical Physical  
Name Name  
NativeType Query Field,BuildIn, Parameter Value  
ReportChart Image  
Name Name  
ReportDataSet Fields, Parameters, Query  
Description Description  
Name Name  
ReportField Field  
Name Name  
ReportList List  
Name Name  
ReportMatrix Matrix  
Name Name  
ReportPage Page  
Name Name  
ReportPageBody Subreport  
Name Name  
ReportPageFooter Subreport  
Name Name  
ReportRectangle Rectangle  
Name Name  
ReportTable Table  
Name Name  
ReportText Textbox  
Name Name  
StoreConnection Database  
DesignLevel Logical Physical  
Name Name  
NativeType Catalog  
StoreModel Report  
Description Description  
DesignLevel Logical Physical  
Name File Name  
NativeType Report