Skip to main content Skip to complementary content

Microsoft SQL Server Analysis (SSAS) and Reporting Services (SSRS) (Repository) - Import

Availability-note AWS

Bridge Requirements

This bridge:
  • requires Internet access to https://repo.maven.apache.org/maven2/ and/or other tool sites to download drivers into <TDC_HOME>/data/download/MIMB/.

  • is only supported on Microsoft Windows.

  • requires the tool to be installed to access its SDK.

Bridge Specifications

Vendor Microsoft
Tool Name SQL Server Analysis and Reporting Services (SSAS, SSRS)
Tool Version 9.0 (2005) to 15.x (2019)
Tool Web Site https://docs.microsoft.com/en-us/analysis-services/
Supported Methodology [Business Intelligence] Multi-Model, Metadata Repository, Data Store (Physical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure) via .Net API
Data Profiling
Incremental Harvesting
Multi-Model Harvesting
Remote Repository Browsing for Model Selection

SPECIFICATIONS
Tool: Microsoft / SQL Server Analysis and Reporting Services (SSAS, SSRS) version 9.0 (2005) to 15.x (2019) via .Net API
See https://docs.microsoft.com/en-us/analysis-services/
Metadata: [Business Intelligence] Multi-Model, Metadata Repository, Data Store (Physical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), BI Design (RDBMS Source, OLAP Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure)
Component: MicrosoftSqlServerRepositoryAsRs version 11.2.0

DISCLAIMER
This import bridge requires internet access to download third-party libraries:
- such as https://repo.maven.apache.org/maven2/ to download open source third-party libraries,
- and more sites for other third-party software such as database specific JDBC drivers.

The downloaded third-party libraries are stored into $HOME/data/download/MIMB/
- If HTTPS fails, the import bridge then tries with HTTP.
- If a proxy is used to access internet, you must configure that proxy in the JRE (see the -j option in the Miscellaneous parameter).
- If the import bridge does not have full access to internet, that $HOME/data/download/MIMB/ directory can be copied from another server with internet access where the command $HOME/bin/MIMB.sh (or .bat) -d can be used to download all third-party libraries used by all bridges at once.

By running this import bridge, you hereby acknowledge responsibility for the license terms and any potential security vulnerabilities from these downloaded third-party software libraries.

OVERVIEW
The bridge imports Reports and Analysis (OLAP Models) databases from a corresponding SQL Server Repository using the SQL Server SDK APIs, including the Reporting Services Web Service and Analysis Management Objects (AMO).

Once all of the metadata is imported, the Analysis database Models will be stitched (mapped for lineage reporting) to the associated Reports.

SUPPORT:
When experiencing issues with the bridge, you should report the issues in a manner that is reproducible by the support engineers. In order to provide a complete set of source metadata to reproduce the issue, please export and attach the Report (RDL) and Analysis Databases (XMLA) files. As always, attach the MIMB Log file, as well.
REQUIREMENTS
In order for this bridge to connect to the SQL Server Repositories and import, it is necessary to ensure that the SQL Server is installed properly and corresponding services are running. As well you need to have installed IIS 5.0 or later. Make sure that you are able to connect to the Reporting Service through Microsoft Internet Explorer 6.0 SP1 or later. This bridge connects to the SQL Analysis Services using the Analysis Services Management Objects (AMO). AMO client libraries are available as installable packages from NuGet.org and the bridge loads it automatically with Miscellaneous -d. You have to install these components with first running. The bridge uses Windows Authentication to connect to Report and Analysis Services. Please be sure the application is logged into Windows Domain as a User which has appropriate rights to the objects you wish to import.

FREQUENTLY ASKED QUESTIONS
Q. How should I select which metadata is imported?
A. In the Data Sources bridge parameter you should choose a set of DataSources.

Q. How do I prevent the Analysis databases from importing?
A. Leave the Analysis Server bridge parameter empty.

Q. How do I import the entire Report Service Repository content?
A. Enter a '/' into Data Source(s) bridge parameter.

LIMITATIONS
Refer to the current general known limitations at http://metaintegration.com/Products/MIMB/MIMBKnownLimitations.html or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

SUPPORT
Provide a troubleshooting package with debug log. Debug log can be set in the UI or in conf/conf.properties with MIR_LOG_LEVEL=6


Bridge Parameters

Parameter Name Description Type Values Default Scope
Report Server URL Report server well-formed URL starting with http:// or https://. For report server running in native mode, the path to the report server where the necessary reports are located (e.g. http://servername/reportserver or http://servername:portnumber/reportserver). For report server running in SharePoint integrated mode, the URL of the SharePoint site where the reports are deployed, e.g. http://servername) STRING   http://localhost/ReportServer Mandatory
Report Server User The User value can be a user name, a client id, or others (it can even be empty) depending on the authorization method. Refer to the AUTHORIZATION section of this bridge's main documentation. STRING     Mandatory
Report Server Secret The Secret value can be a password, a secret id, or others (it can even be empty) depending on the authorization method. Refer to the AUTHORIZATION section of this bridge's main documentation. PASSWORD     Mandatory
Report Server content List of paths in the report repository which identifies reports, data sources, folders to import, e.g.

Single path: /Testing/Sales Order Detail

Multiple paths as a semicolon-separated list: /Testing/Sales Order Detail;/Testing/Private Sources/Multi Source Reports/R_2

The entire repository: /

To select all reports in a folder and its sub-folders please specify the folder path. To select all reports that use a shared data source please specify the data source path. If the data source type is 'Microsoft SQL Server Analysis Services' please specify its address in the Analysis Server instance parameter.
REPOSITORY_SUBSET   /* Mandatory
Analysis Server instance Analysis server instance to connect to (e.g. hostname or hostname\\instance). Keep empty if reports do not source from Analysis Server databases. STRING      
Miscellaneous MODEL IMPORT OPTIONS
-backup <directory>

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

DATA CONNECTION OPTIONS
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 option 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:
ACCESS
CASSANDRA
DB2
DENODO
HIVE
MYSQL
NETEZZA
ORACLE
POSTGRESQL
PRESTO
REDSHIFT
SALESFORCE
SAP HANA
SNOWFLAKE
SQL SERVER
SYBASE
TERADATA
VECTORWISE
VERTICA

-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

-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"

ANALYSIS SERVER OPTIONS
-library.packageId

Specify packageId for NuGet package with Microsoft.AnalysisServices.dll.
Default value is "Microsoft.AnalysisServices.retail.amd64".

-library.version

Specify version for NuGet package with Microsoft.AnalysisServices.dll.
Default value is "19.20.1".

-library.filter

Specify filter for DLLs inside NuGet package. Result must include "Microsoft.AnalysisServices.dll".
Default value is "/lib/net45/".

-connection.embedded

Enables processing for embedded data sources.
An embedded data source, also known as a report-specific data source, is a data connection that is saved in the report definition. Embedded data source connection information can be used only by the report in which it is embedded.

-d

Specify to download NuGet packages if missing. Cache on first download, then reuse.

-cache.clear

Clears the cache before the import, and therefore will run a full import without incremental harvesting.
STRING      

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Microsoft SQL Server Analysis (SSAS) and Reporting Services (SSRS) (Repository)"
Metamodel
MicrosoftSqlServerRepositoryAsRs
Mapping Comments
     
AggregationRule AggregateFunction A string defined in the measure
Rule Value  
Attribute Table Field  
Name Name  
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
Name Name  
ClassifierMap DataSet  
Name name  
Cube Cube  
Description Description  
Name Name  
NativeId ID  
PhysicalName Name  
CubeDimensionAssociation OLAPCubeDimension Defined by containment relationship between Cube and Dimension
DataAttribute SQL/MDX Item  
Name name  
Position position  
DataSet SQL/MDX Query  
Name name  
DatabaseSchema Database Schema  
Name Name  
DerivedType Database Field Datatype Report Field Datatype  
DataType Datatype  
Length length  
Name   Derived from the datatype
PhysicalName   Derived from the datatype
Dimension Dimension  
Description Description  
Hide visible  
Name Name  
NativeId ID  
NativeType Type  
PhysicalName Name  
DimensionAttribute DimensionAttribute  
Description Description  
Name Name  
NativeId ID  
PhysicalName Name  
DirectoryStructureModel Repository  
Name name  
FeatureMap   FeatureMap objects are used to hold the lineage of QueryItems DataAttributes, ReportDataAttributes
Operation expression text  
Folder Folder  
Description description  
Name name  
Hierarchy Hierarchy  
Description Description  
Name Name  
NativeId ID  
PhysicalName Name  
HierarchyLevelAssociation OLAPHierarchyLevel Defined by containment relationship between hierarchy and level
Name Name  
Join Relationship Defined by DataSourceView
Description Description  
Name Name  
NativeId ID  
Type Type  
JoinRole   Defined by the relationship
Level Level  
Description Description  
Name Name  
NativeId ID  
NativeType Type  
PhysicalName Name  
LevelAssociation OLAPHierarchyAssociation Defined by the contiainment between Level and Attribute
Name Name  
LevelAttribute DimensionAttribute Contained by a Level
Description Description  
Name Name  
NativeId ID  
Optional Usage (Attribute)  
PhysicalName Name  
LevelKey ValueColumn  
Description Description  
Name Name  
NativeId ID  
NativeType Type  
PhysicalName Name  
Measure Measure  
DefaultAggregation AggregationString  
Description Description  
Hide visible  
Name Name  
NativeId ID  
NativeType Type  
PhysicalName Name  
ModelVersion AS Database, RS Report  
Name name  
MultiModelVersion Folder  
Description description  
Name name  
OlapSchema OLAP DataBase  
Name Name  
Report Report  
Description Description  
Name Name  
ReportAttribute ReportField  
Name Name  
ReportChart Image  
Name Name  
ReportDataSet DataSet  
Description Description  
Name Name  
ReportField Field  
Name Name  
ReportList List  
Name Name  
ReportMatrix Matrix  
Name Name  
ReportPage Subreport  
Name Name  
ReportPageBody Subreport  
Name Name  
ReportPageFooter Subreport  
Name Name  
ReportRectangle Rectangle  
Name Name  
ReportTable Table  
Name Name  
ReportText Textbox  
Name Name  
StoreConnection Database  
Name Name  
StoreContent AS Database, RS Report  
Name name  
Description Description  
Name File Name  

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!