Microsoft SQL Server Reporting Services (File) bridge reference.

About this bridge

The Microsoft SQL Server Reporting Services (File) bridge imports business intelligence models and reports from Microsoft SQL Server Reporting Services, versions 9 through 10.5.

Import parameters

The Microsoft SQL Server Reporting Services (File) bridge uses the following import configuration parameters.

Reporting services file

Required. Specify a report file with the extension .rdl or .rptproj.

Analysis services File

Specify an analysis service file with the extension .xmla or .asdatabase. This file contains cube or dimensional information that is necessary to connect the imported assets in InfoSphere® Information Server.

Import levels

You can import levels and hierarchies that are defined in the BI model. By default, levels and hierarchies are not imported.

Metadata consistency check

Perform a consistency check on the selected metadata before it is imported into the metadata repository. It is possible to save metadata in source tools in ways that cause problems when the assets are imported into the metadata repository or used in other tools. For example, a foreign key might have no connection to a primary key or to an alternate key. In some cases, the metadata might be so semantically inconsistent that the bridge cannot import it.

The metadata consistency check returns warnings and errors in the log file.

Basic check

The default. Performs the minimum consistency checks necessary to validate the metadata, including checking for missing relationships and foreign keys that are not connected to primary or alternate keys.

In some cases, the basic check might be more rigorous than necessary and you can ignore certain errors or warnings.

Detailed check

Performs the basic check plus more advanced semantic checks specific to the type of metadata that is imported. This level can be used when the source tool does not have the ability to validate the metadata.

No check

Use with extreme caution. Selecting this option could result in the import of duplicates or invalid identities and might cause serious problems with your use of suite tools and the metadata repository.