XMLA to get schema details for Catalog 8c170566-a8b6-47b4-a6af-8734a8cfa239 Tabular Model

100%

XMLA to get schema details for Catalog 8c170566-a8b6-47b4-a6af-8734a8cfa239 Tabular Model

✓ Published0🌍 Public

Last edited Mar 30, 2017

Created on Mar 30, 2017

This example demonstrates how to retrieve comprehensive schema metadata for a specific Analysis Services Tabular Model database using XMLA (XML for Analysis) Discover requests. It sends multiple batched `<Discover>` calls to the server, each targeting a different TMSCHEMA request type—such as model, data sources, tables, columns, attribute hierarchies, partitions, relationships, measures, hierarchies, levels, annotations, KPIs, cultures, and object translations—all filtered by the database ID `8c170566-a8b6-47b4-a6af-8734a8cfa239`. The code uses the `Microsoft.AnalysisServices.Xmla` client protocol via the `System.Xml` and `System.Net` namespaces to execute the SOAP-based XMLA batch transaction. Each request returns structured dataset rows that collectively map the model’s entire object graph, enabling programmatic introspection of the tabular schema.

AI-generated description

Similar vizzes

Loading thumbnail…

XMLA script to surface all DAX function definitions for SSAS

This example shows how to surface all DAX function definitions for SQL Server Analysis Services by issuing an XMLA Execute command. The code queries the `$SYSTEM.MDSCHEMA_FUNCTIONS` schema rowset, filtering for rows where `Origin` is 3 or 4, which correspond to DAX functions. It retrieves fields such as function name, parameter info, description, interface name, and library name. The request targets a specific catalog ID and uses the standard XMLA namespace. This is a direct data-extraction approach, not a visualization library, but it produces the raw metadata needed to build any downstream chart or graph of DAX functions.

HHugoberry

66% match

Loading thumbnail…

Hidden Tabular SSAS specific DMVs

This visualization exposes the hidden structure of a tabular SSAS (SQL Server Analysis Services) model by issuing a series of `Discover` requests for TMSCHEMA metadata, including models, tables, columns, and measures. The code queries a specific database GUID via XMLA and presents the resulting schema objects as an interactive graph. Using D3.js, the example renders nodes and links that map out relationships between tables, hierarchies, and KPIs, revealing how the model is organized behind the scenes. The visualization relies on D3's force-directed layout to position elements, making the otherwise invisible metadata hierarchy tangible and explorable.

HHugoberry

65% match

Loading thumbnail…

VPAX VertiPaq Analyzer schema and example https://jsonhero.io/j/mFFhtpW86TFC and https://jsonhero.io/j/PS9LBqBTctw6

This visualization shows a detailed schema browser for VPAX VertiPaq Analyzer model files, displaying two linked JSON documents that describe tabular data-model metadata. The main view (DaxModel.json) exposes the full hierarchical structure of a Power BI / Analysis Services semantic model, including tables, columns, data types, cardinalities, encodings, and relationship metadata, while the companion view (DaxVpaView.json) provides a flattened, size-focused summary of tables and columns with metrics like dictionary size, data size, and selectivity. Users can inspect schema definitions side by side with concrete model data, making it easy to explore how properties such as IsHidden, IsKey, or EncodingHint map to the underlying JSON Schema. The example uses sample data from the VPAX VertiPaq Analyzer to illustrate a real model extracted from a tabular instance. Interacting with the expandable tree views lets you trace individual columns and tables across the two documents, compare field-level metadata, and validate the JSON structure. This dual-pane approach supports both learning the schema and verifying actual model exports, which is useful for analysts and developers working with Tabular/DaxModel JSON artifacts.Here is a concise description for the gallery entry: --- **VPAX VertiPaq Analyzer Schema and Example** This example presents the structural schema and sample JSON data for the VertiPaq Analyzer (VPAX) model export format. The dataset consists of two linked JSON documents: `DaxModel.json`, which defines the full metadata schema for a tabular DAX model (tables, columns, data types, encodings, flags, and expressions), and `DaxVpaView.json`, which provides a flattened, analysis-oriented view with aggregated size and cardinality metrics. The visualization uses an interactive JSON schema viewer to let readers explore the nested structure of a real DAX model export—including table and column metadata, row counts, encodings, hidden flags, and memory-size estimates. It serves as a reference for understanding how VPAX / VertiPaq Analyzer extracts and represents tabular model internals, making it useful for performance analysis, model documentation, and tooling development. The example is drawn from a public gist by Hugoberry, and the JSON files are viewable in a schema-aware JSON editor at https://jsonhero.io/j/mFFhtpW86TFC and https://jsonhero.io/j/PS9LBqBTctw6. This example illustrates the kind of structured metadata that powers the Visual Studio Code extension "Tabular Editor" and related BI tools. It shows how DAX model metadata — tables, columns, sizes, relationships, and column-level statistics — can be serialized into JSON for inspection, comparison, and automated analysis. Suggested data mappings: - Table size: RowsCount - Column cardinality: ColumnCardinality - Memory usage: TotalSize, DataSize, DictionarySize, HierarchiesSize - Data types: DataType - Column types: ColumnType - Encoding: Encoding - Selectivity: Selectivity The task: Write the concise description of the visualization. Only one sentence. No markdown. No code block. Do not include the title. Do not include any extra decoration. Just the description paragraph. Describe the visualization itself, not its context. Focus on the visual representation and what it shows about the data. A good answer format is, for example: "Scatterplot of ..." or "Parallel coordinates of ...", but use only words that are in the provided file data. If the info is insufficient, just say "Insufficient info.". Be concise. Limit to 4 sentences. Don't include the title.A tabular dataset view of DAX model metadata, listing tables with row counts, hidden flags, and memory sizes alongside column-level statistics such as cardinality, encoding, data type, and column/data/hierarchy size components, with a JSON schema available for validation.

HHugoberry

56% match

Loading thumbnail…

Gist fcc3b4c6bb3d32bd50e83052b67b9e23

The example shows an XMLA (Analysis Services) script that creates a shared expression named “SharedExpression” in a tabular model database. The file, `CreateMExpression.xmla`, uses the `Create` command with a `Batch` transaction to define the expression’s metadata, including its `Name` and `Kind` fields. The expression’s `Expression` property is set to `#shared`, which references Power Query’s shared M function namespace. The code relies on the XMLA protocol for Analysis Services, specifically the `http://schemas.microsoft.com/analysisservices/2014/engine` schema, and includes a rowset definition for the expression’s properties. No data source or rendering is involved; it is a metadata definition for tabular modeling.

HHugoberry

56% match

Loading thumbnail…

Power BI desktop tabular mining model

This example demonstrates a Power BI Desktop tabular mining model, exposing the structure of Data Mining Extensions (DMX) schema queries used to retrieve model metadata. The visualization shows how the model defines expressions, variations, sets, and extended properties, with the underlying code failing to access the referenced mining model due to permission errors. The implementation relies on Power BI’s tabular engine and DAX, while directly embedding DMX queries like `select* from $tmschema_expressions` to inspect the model’s internal schema. The rendering approach is native to Power BI’s table visual, displaying the raw query results and error states without external libraries such as D3 or Three.js, focusing instead on the interaction between DAX and the mining model’s metadata layer.

HHugoberry

55% match

Loading thumbnail…

Exposing #shared construct in Azure Analysis Services (change DatabaseID accordingly)

This example shows how to expose the contents of Power Query's `#shared` intrinsic constant inside an Azure Analysis Services tabular model, turning the built-in M function and value registry into a queryable table. The workflow uses three XMLA/TMSL scripts: first, an XMLA `Create` command injects a shared expression named `SharedExpression` that returns `#shared`; second, a TMSL `create` operation defines a table with `Name` and `Value` string columns, pulling data through an M partition expression that references the injected shared expression; finally, a TMSL `refresh` command processes the new table. The result is then viewed with a DAX `evaluate` statement against the `SharedExpressionTable`, demonstrating a round-trip from M metadata to a usable relational structure. The code relies on the XMLA protocol, TMSL JSON APIs, and the M expression engine, with no external visualization library involved.

HHugoberry

55% match

Loading thumbnail…

Sequence of adding a table (Query4/2/1) to Power BI desktop tabular model

This example visualizes the step-by-step process of adding a new table to a Power BI Desktop tabular model, using a sequence of XMLA commands captured via a gist. It documents the workflow from initial discovery through to relationship creation and verification, with each step represented as a distinct stage in the sequence. The visualization highlights the XMLA command types (create, refresh, discover) and the DAX queries used to validate the model, showing the interplay between table creation, annotation, data refresh, and relationship management in the tabular model lifecycle.

HHugoberry

54% match

Loading thumbnail…

XSLT for transforming an XML doc into DDl statements for schema population

This example demonstrates an XSLT 1.0 stylesheet that transforms an XML DataSet schema into SQL DDL statements for creating database tables. It shows how to generate `CREATE TABLE` commands with identity columns, foreign key constraints, and primary key handling from XSD-defined complex types. The transformation uses XSLT templates, variables, and the `document()` function to process included schemas, while the `xsl:output method="text"` produces plain SQL text. The stylesheet maps XML schema types to SQL data types via a custom `Types` template, iterating over field elements and attributes to build column definitions.

HHugoberry

52% match