Skip to main content
Use the @bijection/connectors/ssas entrypoint to declare SQL Server Analysis Services resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Catalogs

discover: The instance’s databases (DBSCHEMA_CATALOGS)

The following example matches configuration standard.

Configuration: standard

Case: ssas/catalogs/discover/standard. Connection and resource configuration are declared by this exact case. Credential kind: ssas. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: catalogs
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Cubes

discover: One catalog’s cubes (MDSCHEMA_CUBES)

The following example matches configuration standard.

Configuration: standard

Case: ssas/cubes/discover/standard. Connection and resource configuration are declared by this exact case. Credential kind: ssas. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: cubes
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Statement

statement: One fixed DAX or MDX statement as a tabular rowset

The following example matches configuration standard.

Configuration: standard

Case: ssas/query/statement/standard. Connection and resource configuration are declared by this exact case. Credential kind: ssas. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: rows
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Read-only XML for Analysis (SOAP 1.1) over the IIS msmdpump.dll HTTP access Microsoft documents for clients that cannot use the Analysis Services client libraries. The connection is the pump URL (endpoint setup, for example https://host/olap/msmdpump.dll); the instance it reaches is the pump’s msmdpump.ini setting. The credential is HTTP Basic, sent over HTTPS: IIS impersonates that Windows account. Windows integrated authentication is not offered by the platform’s credential envelopes. SSAS 2025 refuses a non-HTTPS pump by default. Identity is the ServerName property from DISCOVER_PROPERTIES, the name of the Analysis Services instance. It is a name, not a unique id. Every call POSTs one SOAP envelope (text/xml, documented SOAPAction) with Format=Tabular and Content=Data. Responses are decoded by the host xml codec: local names only, . and - read as _, at most 4,096 elements, depth 16 and 512 KiB, so a larger rowset fails rather than truncates. An in-band XMLA Exception or Messages/Error and a SOAP Fault (HTTP 500) refuse the page. Values stay the rowset’s text, so xsd:decimal is exact as text; an omitted element or xsi:nil is null. catalogs.discover reads DBSCHEMA_CATALOGS. cubes.discover reads MDSCHEMA_CUBES for one catalog, cubes only, publishing lastDataUpdate (last processed) and lastSchemaUpdate. query.statement executes one fixed DAX or MDX statement; the caller names the rowset column elements (XMLA escapes [, ] and spaces as _xHHHH_) and the key columns. None claims coverage and nothing is withdrawn for being absent. Catalog names and the statement are XML-escaped into the request. Azure Analysis Services (asazure://) is not built: it is reached through the client libraries with Entra tokens and documents no pump-style HTTP contract. Nothing here has run against Analysis Services or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.