MicroStrategy - Lineage

This article outlines lineage coverage, configuration requirements, supported components, transformation support, supported use cases, partial or limited coverage, unsupported scenarios, and the current functional status of lineage extraction in MicroStrategy.

The MicroStrategy connector provides automated lineage extraction across Reports, Cubes, Dashboards, Semantic Tables, and physical database objects. It provides end-to-end visibility into data flow from physical source tables through semantic layers and Cubes to Reports and Visualizations. The connector supports column-level lineage and multi-hop lineage across semantic and reporting layers.

Lineage Configuration Requirements

Successful lineage extraction depends on valid SQL dialect configuration, access to physical database metadata, available MicroStrategy metadata, and the required lineage processing configuration. The following requirements apply to MicroStrategy lineage extraction.

Configuration Requirements Table

Configuration	Required Detail
SQL Dialects	SQL dialects must be configured through supportingDialects in CrawlerOption for SQL parsing.
Database Catalog Access	Database catalog access is required to map physical tables and columns to MicroStrategy objects.
MicroStrategy Metadata	Valid JSON SourceCode metadata must be available for Reports and Cubes.
Object ID Decryption	Object ID decryption support is required for lineage processing.
Query Length	MAX_QUERY_LENGTH may require tuning to process large Report queries.
Pre-crawled Metadata	Physical tables, columns, charts, and datasets must be crawled before lineage is built so that lineage relationships can be established.

Missing physical database metadata, unavailable JSON SourceCode metadata, incomplete crawled objects, unsuccessful object ID processing, or Report queries that exceed the configured MAX_QUERY_LENGTH may result in incomplete lineage generation.

Lineage Components

The following table identifies the MicroStrategy components and lineage features supported by the connector.

Component / Feature	Supported
Reports	✅
Cubes	✅
Dashboards	✅
Visualizations	✅
Semantic Tables	✅
Physical Tables	✅
Physical Columns	✅
Report Columns	✅
Metrics	⚠️
Attributes	⚠️
Derived Metrics	⚠️
SQL Queries	✅
Alias Mapping	⚠️
Dynamic SQL	⚠️
Multi-hop Lineage	✅
Runtime Execution Lineage	❌

The ⚠️ icon indicates partially supported functionality where lineage coverage depends on metadata availability, SQL parsing capability, query complexity, or the specific MicroStrategy implementation.

Column Creation Support

This section outlines lineage support for columns created through SQL expressions, semantic-to-physical mappings, aliases, formulas, aggregations, temporary objects, and logical columns.

Column Creation from Lineage

Transformation Type	Supported
SQL-derived Columns	✅
Semantic-to-Physical Column Mapping	✅
Renamed/Alias Columns	⚠️
Derived Metrics/Formulas	⚠️
Aggregate Columns	⚠️
Temp Columns	✅
Logical Columns	✅
Runtime-generated Columns	❌

The ⚠️ icon indicates partial column-level lineage coverage. Resolution depends on SQL parser capability, formula complexity, alias structure, and the availability of required metadata.

Supported Use Cases

The MicroStrategy connector supports lineage extraction across physical database objects, semantic layers, Reports, Cubes, Dashboards, and Visualizations.

Supported Lineage Scenarios

Supported Scenario	Details
Physical Table → Semantic Table Lineage	Lineage from physical database tables to corresponding MicroStrategy Semantic Tables.
Semantic Table → Report Lineage	Lineage from Semantic Tables to Reports that reference the corresponding semantic objects.
Cube → Report → Dashboard Lineage	Multi-hop lineage across Cubes, Reports, and Dashboards.
Report → Visualization Lineage	Lineage between MicroStrategy Reports and associated Visualizations.
SQL-based Report Lineage	Lineage extraction from SQL-based Reports using SQL parsing and supported alias mapping.
Multi-source Report Lineage	Lineage across Reports that reference multiple source systems or physical sources.
Sub-report / Chart-to-Chart Lineage	Lineage between supported sub-reports, charts, and related reporting objects.
Logical-to-Physical Column Mapping	Column-level lineage between logical or semantic columns and physical database columns.
Column-level Lineage for Reports and Cubes	Column-level lineage across supported Reports, Cubes, and source objects.
Multi-hop Lineage	End-to-end lineage across physical, semantic, analytical, and reporting layers.
SQL Query Lineage	Lineage from source tables and columns through available SQL query definitions.

Lineage extraction depends on crawled physical database metadata, available MicroStrategy JSON SourceCode, SQL parsing, object resolution, and the ability to establish relationships across semantic and reporting layers.

Partial or Limited Coverage

Certain MicroStrategy scenarios provide partial lineage coverage because formula complexity, dynamic query generation, alias structures, metadata availability, or query size can limit complete lineage resolution.

Scenarios

Scenario	Limitation Description	Recommendation / Workaround
Calculated Metrics	Complex metric formulas may not fully resolve into individual source-to-target lineage relationships.	Validate complex metric dependencies manually where detailed transformation lineage is required.
Derived Columns	Formula parsing relies on text matching and may not resolve complex derived-column logic completely.	Validate derived-column dependencies manually where required.
Aggregations and Window Functions	Support depends on the capabilities of the configured SQL parser and the SQL structure.	Validate aggregation and window-function lineage manually for complex queries.
Dynamic SQL	Runtime-generated queries may not be resolved when the required SQL is not available in metadata.	Use statically available SQL definitions where possible and validate dynamic dependencies separately.
Alias Resolution	Complex aliases and aliases containing special characters may not resolve correctly.	Use clear and consistent aliases where possible and validate affected column mappings manually.
Non-SQL Objects	Metadata-only lineage may be available when complete SQL definitions are not available.	Validate source dependencies separately when complete SQL-level lineage is required.
Large Queries	Reports that exceed the configured MAX_QUERY_LENGTH may be skipped during lineage processing.	Review and tune MAX_QUERY_LENGTH where required for large Report queries.
AI-based Fuzzy Matching	Fuzzy matching functionality is present in the code but is currently disabled.	Use exact or supported matching methods and validate unresolved column relationships manually.
Missing Metadata	Temporary objects created with incomplete metadata may result in partial lineage.	Ensure relevant metadata is available and validate temporary-object lineage where required.

Complex metric formulas, derived columns, aggregation logic, dynamic SQL, complex aliases, large queries, disabled fuzzy matching, and incomplete metadata may reduce lineage completeness and column-level accuracy.

Unsupported Scenarios

The connector does not support complete lineage extraction for runtime-generated SQL, execution-level lineage, advanced formula decomposition, unresolved physical sources, and certain metadata processing scenarios.

Unsupported Lineage

Not Supported	Description	Recommendation / Workaround
Runtime-generated SQL	SQL generated at runtime is not available for lineage extraction when the required SQL is not present in metadata.	Use statically available SQL definitions where possible and validate runtime dependencies separately.
Advanced Formula Decomposition	Complex calculated formulas cannot be fully decomposed into individual source-column lineage relationships.	Validate complex formula dependencies manually where expression-level lineage is required.
Execution / Runtime Lineage	Lineage based on actual runtime execution is not supported.	Use metadata-based lineage and validate runtime data flows separately where required.
Automatic Fuzzy Matching	Automatic fuzzy matching for unresolved columns is currently disabled.	Use supported exact or normalized matching and validate unresolved relationships manually.
Uncrawled Physical Databases / Tables	Lineage cannot be established for physical databases or tables that are not available in the crawled catalog.	Crawl the required physical databases and tables before building lineage.
Complete Analytical Engine SQL Context	Complete preservation of analytical engine SQL context is not supported for all lineage scenarios.	Validate analytical-engine-specific transformations separately where required.
Automatic Encrypted Metadata Failure Handling	Automatic handling of encrypted metadata failures is not supported.	Resolve metadata access or decryption issues before lineage extraction.
Runtime-generated Columns	Columns created dynamically at runtime are not supported for lineage creation.	Validate runtime-generated column dependencies separately where required.

Unsupported scenarios do not generate complete lineage and may result in missing or disconnected lineage relationships within lineage visualization.

Current Functional Status

This section outlines the current lineage capabilities and coverage of the MicroStrategy connector.

Status Area	Details
Overall Coverage	Partial coverage across MicroStrategy Reports, Cubes, Dashboards, Semantic Tables, physical database objects, and supported SQL-based lineage scenarios.
Lineage Depth	Table-level, semantic-level, report-level, visualization-level, and column-level lineage across supported MicroStrategy objects.
Supported Inputs	Reports, Cubes, Dashboards, Visualizations, Semantic Tables, Physical Tables, Physical Columns, Report Columns, SQL Queries, and supported metadata objects.
Functional Scope	End-to-end lineage from physical source tables through semantic layers and Cubes to Reports, Dashboards, and Visualizations, including multi-hop and column-level lineage.
Transformation Support	SQL-derived columns, semantic-to-physical column mappings, temporary columns, logical columns, and supported SQL transformations are handled.
Limitation Areas	Calculated Metrics, Derived Columns, Aggregations, Window Functions, Dynamic SQL, Alias Resolution, Non-SQL Objects, large queries, and incomplete metadata have partial coverage.
Unsupported Areas	Runtime execution lineage, advanced formula decomposition, automatic fuzzy matching, lineage for uncrawled physical sources, complete analytical engine SQL context preservation, and runtime-generated columns are not supported.
Resulting Output	Reliable lineage across core MicroStrategy reporting, semantic, and physical database scenarios, with partial coverage for complex formulas, dynamic SQL, aliases, and advanced metadata interpretation.

The MicroStrategy connector provides reliable lineage across Reports, Cubes, Dashboards, Semantic Tables, physical database objects, SQL queries, and supported column-level and multi-hop lineage scenarios. SQL-derived columns, semantic-to-physical mappings, temporary columns, logical columns, and supported SQL transformations are handled. Complex formulas, derived metrics, aggregations, dynamic SQL, complex alias mapping, large queries, incomplete metadata, and advanced analytical-engine SQL interpretation have partial or unsupported coverage. Runtime execution lineage and runtime-generated columns are not supported and may require separate validation or manual lineage supplementation.

---

Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA