exasol-semantic-modeler

Derives, authors, validates, and publishes Exasol Semantic Views models from physical schemas.

3|Updated May 14, 2026
One-click install
npx skills add https://github.com/exasol-labs/exasol-semantic-views --skill exasol-semantic-modeler-exasol-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: exasol-semantic-modeler
Source: https://github.com/exasol-labs/exasol-semantic-views/tree/main/skills/exasol-semantic-modeler
Command: npx skills add https://github.com/exasol-labs/exasol-semantic-views --skill exasol-semantic-modeler-exasol-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building a governed semantic layer by hand requires inspecting physical schemas, inferring grain and relationships, and writing correct metric DDL — a slow, error-prone process. This Skill automates the derivation and maintenance of Exasol Semantic Views models so agents and analysts get deterministic, governed metrics. ## Core Features & Use Cases - Autonomous model derivation: Inspects tables, views, column comments, and historical query logs (EXA_DBA_AUDIT_SQL, profiling tables) to propose entities, relationships, facts, dimensions, and metrics in dependency order. - Full authoring lifecycle: Creates models, registers entities and grain proofs, authors additive/filtered/ratio/derived/window metrics, validates with VALIDATE_MODEL, and publishes governed semantic views. - Migration and fusion support: Imports Databricks Unity Catalog Metric Views and manages multi-representation fusion (F1 equivalents, F3 hot/cold partitions, F4 reconciliation, F5 identity mapping). - Use Case: Point the agent at a MART schema with order and customer tables; it inspects comments and workload history, derives a sales model with revenue and margin metrics, validates it, and publishes it for SQL, BI, and agent consumption. ## Quick Start Use the exasol-semantic-modeler skill to inspect the MART schema, derive a semantic model with entities, relationships, and metrics, validate it, and publish it as an Exasol Semantic Views model.

Frequently Asked Questions about exasol-semantic-modeler

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a semantic model in Exasol from existing tables?▼

Inspect the schema via EXA_ALL_TABLES and EXA_ALL_COLUMNS, then call SEMANTIC_ADMIN.CREATE_MODEL followed by ADD_ENTITY, ADD_UNIQUE_KEY, ADD_RELATIONSHIP, ADD_FACT, ADD_DIMENSION, and metric DDL in dependency order. Finish with VALIDATE_MODEL and PUBLISH_MODEL.

How to import a Databricks Unity Catalog Metric View into Exasol?▼

Run SEMANTIC_ADMIN.IMPORT_DATABRICKS_METRIC_VIEW with the metric view YAML, target model, and FALSE as the apply flag for a dry run. Review the generated DDL and diagnostics, then rerun with TRUE to create, validate, and publish the model.

Can I query Exasol audit history to design better metrics?▼

Yes. EXA_DBA_AUDIT_SQL, EXA_DBA_PROFILE_LAST_DAY, and SYS_SEMANTIC.QUERY_LOG reveal repeated GROUP BY columns, filters, and aggregation patterns. Use them to prioritize dimensions, filtered metrics, and synonyms, but let physical grain and constraints override usage evidence.

Why does Exasol model validation fail with SEMANTIC_MODEL_033?▼

SEMANTIC_MODEL_033 occurs when relationship key mappings are added before the required unique key is fully declared. Declare ADD_UNIQUE_KEY and all ADD_UNIQUE_KEY_COLUMN components first, then add the relationship and its mappings, and rerun VALIDATE_MODEL.

What privileges are required for Exasol semantic model authoring?▼

All SEMANTIC_ADMIN scripts require EXECUTE SCRIPT through a full-privilege SQL connection, not a SELECT-only tool. Reading discovery views and schema metadata needs only SELECT, while DBA-prefixed history tables require SELECT ANY DICTIONARY.

When should I not use F3 hot/cold partition fusion in Exasol?▼

Avoid F3 when the entity is only a joined dimension, when metrics use AVG, distinct, or window aggregates, or when snapshots overlap. F3 applies only to metric-leaf entities with mergeable SUM or COUNT metrics and contiguous half-open coverage intervals.