Prerequisites, troubleshooting, and parameter information for the Microsoft SQL Server Analysis and Reporting Services (Repository) 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.
To use the latest version of this bridge, you must install the prerequisite software: http://www.ibm.com/support/docview.wss?uid=swg27038230.
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.
You specify values for the following parameters during imports.
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.
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.
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.
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.
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.