Adding an SSAS (SQL Server Analysis Services) Connection
Prerequisites
A user with sufficient
permissions is required to establish a connection with SSAS.
Installing the Plugin
Declaring the Connection
Creating and configuring connectors is done through a dedicated configuration file located in the /connections folder of the relevant scanner.
In order to establish a connection with SSAS, the following parameters in the dedicated file are required:
Parameter | Expected value |
|---|
name | The name that will be displayed to catalog users for this connection. |
code | The unique identifier of the connection on the Zeenea platform. Once registered on the platform, this code must not be modified or the connection will be considered as new and the old one removed from the scanner. |
connector_id | The connector type to use for the connection. Here, the value must be ssas and this value must not be modified. |
connection.path | Path to the SSAS project directory to synchronize with the catalog. These files will be parsed: - .cube : cube file - .ds: reference datasource file - .dsv: reference datasource view file |
connection.url | URL to the data pump MSMDPUMP.dll |
connection.server_mode | Server or project mode for SSAS. Accepted values are: - Empty or tabular: The target server/project is configured in "Tabular" mode. - multidimensional: The target server/project is configured in "Multidimensional" mode. |
Note: A template of the configuration file is available in
this repository.
User Permissions
In order to collect metadata, the running user's permissions must allow them to access and read files from the directory specified in the dedicated parameter.
When the URL parameter is configured, the connector goes through the MSMDPUMP.dll data pump.
Data Extraction
To extract information, the connector runs requests on views from the pg_catalog schema.
Collected Metadata
Lineage
The connector only handles lineage from SQL queries. M scripts are not handled.
The connector is capable of reconstructing the lineage of manipulated tables in transformations if they are present in the catalog. This functionality is available when SSAS manipulates datasets from the following technologies:
In this case, it is necessary to specify an additional parameter in the original connections of these tables following the format:
alias = ["<host>:<port>/<database>"]
where the variables <host>, <port>, and <database> are replaced with the values from the original connections.
Dataset
A dataset corresponds to a table for a SSAS server in "Tabular" mode or a cube for a server in "Multidimensional" mode.
Name
Source Description
Technical Data:
Catalog
Creation date
Last modification date
Field
A field is a field within a dataset.
Data Process
A data process represents lineage between a cube/table and its sources.
Name: CREATEVIEW view-name
Input: Datasets as input to the process
Output: Dataset as output to the process
Technical Data:
Object Identification Keys
An identification key is associated with each object in the catalog. In the case of the object being created by a connector, the connector builds it.
Object | Identification Key | Description |
|---|
Dataset | code/catalog/[table or cube] | - code: Unique identifier of the connection noted in the configuration file - catalog: Name of the catalog - table or cube: Name of the table or cube |
Field | code/catalog/[table or cube]/column | - code: Unique identifier of the connection noted in the configuration file - catalog: Name of the catalog - table or cube: Name of the table or cube - column name: Name of the column, the measure, or the dimension |
Data process | code/catalog/dataprocess/import [table or cube] | - code: Unique identifier of the connection noted in the configuration file - catalog: Name of the catalog - transformation: Name of this transformation |
Last modified date: 11/28/2025