Microsoft SQL Server Analysis and Reporting Services (Repository) bridge reference

Prerequisites, troubleshooting, and parameter information for the Microsoft SQL Server Analysis and Reporting Services (Repository) bridge.

About this bridge

The Microsoft SQL Server Analysis and Reporting Services (Repository) bridge imports metadata from versions 9.0 (2005) to 11.0 (2012) of Microsoft SQL Server Analysis Services (SSAS) and Microsoft SQL Server Reporting Services (SSRS). The imported metadata includes BI models, BI reports, and the implemented data resources that the reports source data from, such as database tables.

The bridge uses the SQL Server SDK APIs, including the Reporting Services Web Service and Analysis Management Objects (AMO) to import the metadata from the repository. The bridge preserves the relationships between the reports and the database metadata in the metadata repository. Preserving the relationships enables data lineage in InfoSphere® Metadata Workbench.

Prerequisites

To use the latest version of this bridge, you must install the prerequisite software: http://www.ibm.com/support/docview.wss?uid=swg27038230.

Meet the following prerequisites before you run the bridge:
  • To connect to the SQL Server repositories and to import, SQL Server must be installed properly and the services must be running.
  • Microsoft Internet Information Services (IIS) version 5.0 or later must be installed.
  • Ensure that you are able to connect to the Reporting Service through Microsoft Internet Explorer 6.0 SP1 or later.
  • Metadata Integration Bridges must be installed on the same computer on which the SQL Server services are installed.
  • The bridge uses Windows authentication to connect to the report and analysis services. Ensure that the log-on account for the IBM InfoSphere Metadata Interchange Server service has the appropriate rights to the objects that you want to import. Use the same credentials that you would normally use to connect to the services.

Troubleshooting

To provide support with complete source metadata to reproduce an issue, export and attach the files from the report database (.rdl) and analysis database (.xmla). Also attach the import log file.

Import parameters

You specify values for the following parameters during imports.

SQL Server version
Specify the version of Microsoft SQL Server Report and Analysis services to connect to, SQL Server 2005, 2008 or 2012.
Report server URL

Type a well-formed URL to the report server, starting with http:// or https://.

For a report server that is running in native mode, type the path to the report server where the reports are located, for example, http://servername/reportserver or http://servername:portnumber/reportserver.

For a report server that is running in SharePoint integrated mode, type the URL of the SharePoint site where the reports are deployed, for example, http://SharePoint_site.

Assets to import

Browse to select the reports, data sources, or folders to import.

Alternately, you can type the paths in the report repository that identify reports, data sources, or folders to import. Use semicolon (;) to separate paths.

Examples:
  • Single path: /Testing/Sales Order Detail
  • Multiple paths: /Testing/Sales Order Detail;/Testing/Private Sources/Multi Source Reports
  • Entire repository: /
    Note: For performance reasons, do not import the entire repository.
To select all reports in a folder and its subfolders, specify the folder path. To select all reports that use a shared data source, specify the data source path. If the data source type is Microsoft SQL Server Analysis Services, specify its address in the Analysis server instance parameter.
Analysis server instance

Specify the analysis server instance to connect to. For example, specify the host name or specify host_name\instance.

Leave this field empty if the reports do not source from an analysis server database or if you do not want to import content from the analysis server.

Incremental import

Keep this parameter selected. When you reimport from the same source, the bridge uses cached information to determine which objects did not change since the previous import. Only changed objects are reimported. Using the cached information can increase performance for large imports.

For new imports, or when the cache is deleted or corrupted, the bridge imports all objects from the source regardless of the selection that is specified.

Import joins
You can import joins that are defined in the BI model. By default, joins are not imported.
Import levels
You can import levels and hierarchies. When the option is selected, levels and hierarchies that are defined in the BI model are imported. By default, they 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.