Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from Microsoft SQL Server Reporting Services (SSRS) (Repository)

Bridge Specifications

Vendor Microsoft
Tool Name SQL Server Reporting Services (SSRS)
Tool Version 9.0 (2005) to 15x (2019)
Tool Web Site https://docs.microsoft.com/en-us/sql/reporting-services/
Supported Methodology [Business Intelligence] Metadata Repository, Data Store (Physical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure) via .Net API

SPECIFICATIONS
Tool: Microsoft / SQL Server Reporting Services (SSRS) version 9.0 (2005) to 15x (2019) via .Net API
See https://docs.microsoft.com/en-us/sql/reporting-services/
Metadata: [Business Intelligence] Metadata Repository, Data Store (Physical Data Model, OLAP Dimensional Model, Stored Procedure Expression Parsing), BI Report (Relational Source, Dimensional Source, Expression Parsing, Report Structure)
Component: MicrosoftSqlServerRepositoryRs 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 SSRS Reports from a corresponding SQL Server Repository using the SQL Server SDK APIs.

REQUIREMENTS
In order for this bridge to connect to the SQL Server Repository and import, it is necessary to ensure that the SQL Server Client Components are installed properly and corresponding services are running locally or in your local network. The bridge uses Windows Authentication to connect to Reporting 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
n/a

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_MODEL     Mandatory
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.
STRING      

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"Microsoft SQL Server Reporting Services (SSRS) (Repository)"
Metamodel
MicrosoftSqlServerRs
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  

Last updated on Tue, 6 Feb 2024 17:44:43

Copyright © 1997-2024 Meta Integration Technology, Inc. All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.