<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dainius Remeika</title>
    <description>The latest articles on DEV Community by Dainius Remeika (@danremake).</description>
    <link>https://dev.to/danremake</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4170599%2Ff0ca326a-2132-4542-a34b-a18254e7767c.jpg</url>
      <title>DEV Community: Dainius Remeika</title>
      <link>https://dev.to/danremake</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/danremake"/>
    <language>en</language>
    <item>
      <title>Best Semantic Layer Tools (2026): SQLDBM, dbt MetricFlow, Cube &amp; AtScale Compared</title>
      <dc:creator>Dainius Remeika</dc:creator>
      <pubDate>Sat, 17 Oct 2026 17:32:30 +0000</pubDate>
      <link>https://dev.to/danremake/best-semantic-layer-tools-2026-sqldbm-dbt-metricflow-cube-atscale-compared-cee</link>
      <guid>https://dev.to/danremake/best-semantic-layer-tools-2026-sqldbm-dbt-metricflow-cube-atscale-compared-cee</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F62zq2308q5ee8rkr0qxs.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F62zq2308q5ee8rkr0qxs.png" alt="header" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The semantic layer went from a niche piece of BI plumbing to one of the most talked-about parts of the modern data stack. Part of it is the AI wave. If you want LLMs and copilots to answer business questions without hallucinating, they need governed definitions of what "revenue" or "active customer" actually means. Part of it is just governance catching up with scale. Teams are tired of five dashboards giving five different numbers for the same metric.&lt;/p&gt;

&lt;p&gt;I spent a few weeks looking into the main contenders for 2026. Some are standalone semantic layers that sit between your warehouse and your BI tools. Some are built into platforms you already use. One of them, SqlDBM, does something none of the others do: it ties the semantic layer directly to the physical schema it's describing.&lt;/p&gt;

&lt;p&gt;Here's how they stack up and which one I'd pick depending on your situation.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Evaluated These Semantic Layer Tools
&lt;/h2&gt;

&lt;p&gt;I looked at six things for each tool: how metrics and dimensions are defined, how definitions stay in sync with the underlying warehouse, which BI tools and APIs are supported, how well it serves AI and LLM use cases, pricing transparency, and real production evidence. I spent more time on tools that showed up repeatedly in enterprise data stacks, and I checked public case studies and docs rather than relying on marketing claims.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. SqlDBM - Best Overall
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" alt="SqlDBM" width="799" height="562"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;The only visual modeling platform that grounds your semantic layer in the physical schema it actually describes.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I went into this comparison expecting a pure-play semantic-layer tool to come out on top. SqlDBM changed my mind. The reason is simple. Every other tool in this roundup, from dbt MetricFlow to Cube to AtScale, builds a semantic layer on top of your warehouse without giving you a governed visual model of the warehouse itself. SqlDBM is the only platform that handles both sides. You design physical schemas visually and layer governed business definitions right on top of them, in a single workspace.&lt;/p&gt;

&lt;p&gt;What that means day to day is that when a column name changes in Snowflake or Databricks, the semantic definitions update with the physical model. No manual sync. No stale metrics drifting out of alignment while nobody notices. Standalone semantic tools can't catch that drift because they don't own the physical layer. Traditional visual modeling tools like erwin or ER/Studio can't catch it because they skip the semantic layer entirely.&lt;/p&gt;

&lt;p&gt;The AI angle also surprised me. SqlDBM's MCP Server exposes governed models and metadata directly to LLMs, so your semantic layer isn't just feeding BI dashboards. It becomes the context layer for AI agents and copilots. Mercadona, Spain's largest supermarket chain, uses the SqlDBM API to auto-generate dbt models deployed to BigQuery and to encode metadata for AI agents across nearly 5,000 governed tables. That's actual production governance, not a demo screenshot.&lt;/p&gt;

&lt;p&gt;Snowflake (300+ clients, Premier Partner Connect member), Databricks (Validated Data Partner), and BigQuery are all supported natively. You can forward-engineer to platform-specific DDL or dbt-compatible YAML straight from the diagram. John Holland Group, one of Australia's largest infrastructure firms, finished a Databricks migration in nine months with SqlDBM as the source of truth for their gold-layer models. PwC reports 25% faster modeling time.&lt;/p&gt;

&lt;p&gt;With 400,000+ users globally and back-to-back Database Modeling Solution of the Year wins at the 2023 and 2024 Data Breakthrough Awards, this isn't a bet on an unknown vendor. If your team is picking a semantic layer and still modeling in a separate tool, SqlDBM closes the gap.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The only visual modeling platform that natively bridges physical schemas and a semantic layer. Standalone tools like dbt MetricFlow, Cube, and AtScale skip visual modeling entirely, and legacy tools skip the semantic layer.&lt;/li&gt;
&lt;li&gt;Schema changes propagate automatically to semantic definitions, eliminating the stale-metric drift that plagues disconnected semantic-layer setups.&lt;/li&gt;
&lt;li&gt;MCP Server exposes governed semantic models directly to LLMs and AI agents. Mercadona already uses SqlDBM to encode metadata for AI agents across nearly 5,000 governed tables.&lt;/li&gt;
&lt;li&gt;Native integrations with Snowflake (300+ clients), Databricks (Validated Data Partner), and BigQuery, with dbt-compatible YAML generation and Git/CI/CD support built in.&lt;/li&gt;
&lt;li&gt;Enterprise-proven at scale: 400,000+ users globally, back-to-back Database Modeling Solution of the Year (2023 and 2024), and PwC reports 25% faster modeling.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The breadth of capabilities (semantic layers, lineage, governance, data vault) creates a learning curve. Newer team members may need a few onboarding sessions to use it fully.&lt;/li&gt;
&lt;li&gt;Cloud-warehouse integrations are best-in-class for Snowflake, Databricks, and BigQuery, but teams on niche or on-prem databases may find fewer connectors than in legacy desktop tools.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; SqlDBM plans are quote-based and scaled to team size, with enterprise packaging, premium support, SSO, and security options available at higher tiers. There's a free tier for modeling and exploring before you commit, no credit card required. Contact sales for a tailored quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. dbt Semantic Layer (powered by MetricFlow)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fymgxnkpz5kjx85ddcwpn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fymgxnkpz5kjx85ddcwpn.png" alt="dbt Semantic Layer (powered by MetricFlow)" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The dbt Semantic Layer sits between your dbt models in the warehouse and whatever downstream tools consume them. Teams define semantic models and metrics in YAML next to their transformation code. MetricFlow, the query engine, turns metric requests into optimized SQL and serves results through JDBC, GraphQL, and other APIs. It integrates with Tableau, Power BI, Hex, Mode, and Google Sheets.&lt;/p&gt;

&lt;p&gt;Because it rides on the same Git and CI workflow as the rest of your dbt project, metric definitions get versioned and reviewed like any other code. For analytics engineering teams that already live in dbt, that's a real win. It also gives LLMs and AI agents a governed set of metric definitions to query instead of raw tables.&lt;/p&gt;

&lt;p&gt;The limitations are honest ones. This is a metrics-centric layer, not a full virtual OLAP engine. There's no built-in caching or pre-aggregation like Cube or AtScale offer, so performance leans on the warehouse. And the hosted API requires a paid dbt Cloud plan.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Metrics live in the same YAML and Git workflow as dbt models, so there's little new tooling to learn.&lt;/li&gt;
&lt;li&gt;MetricFlow handles joins and time-spine logic automatically, which cuts down on hand-written SQL.&lt;/li&gt;
&lt;li&gt;Works with many BI tools and exposes JDBC and GraphQL APIs for custom apps and AI use cases.&lt;/li&gt;
&lt;li&gt;Large community and strong governance through lineage, docs, and CI.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The hosted Semantic Layer API requires a paid dbt Cloud plan and isn't available on the free Developer plan.&lt;/li&gt;
&lt;li&gt;Billing is based on queried metrics, so high-refresh dashboards can blow past plan allowances.&lt;/li&gt;
&lt;li&gt;No native query acceleration or pre-aggregation, so heavy workloads lean on warehouse performance.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Available on paid dbt Cloud plans. Per a December 2025 third-party write-up, the Starter plan is about $100 per developer seat per month and includes 5,000 queried metrics per month. Enterprise includes 20,000 queried metrics per month with custom pricing, and overage pricing isn't public. Read-only users are reportedly not charged. Confirm current rates on dbt's pricing page.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Cube
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faiilhik06h9i68ip63v0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faiilhik06h9i68ip63v0.png" alt="Cube" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Cube is API-first. Data teams define cubes, measures, dimensions, and joins in code (YAML or JavaScript), and Cube exposes them through SQL, REST, GraphQL, and MDX APIs. It connects to most major warehouses, including Snowflake, BigQuery, Databricks, Redshift, and Postgres.&lt;/p&gt;

&lt;p&gt;The thing Cube really leans into is performance. A pre-aggregation engine and caching layer give fast, consistent responses even on large datasets, which makes it well suited to embedded and customer-facing analytics. It also has access control, multi-tenancy, row-level security, and marketed AI features for natural-language querying on top of the governed model.&lt;/p&gt;

&lt;p&gt;The open-source Cube Core can be self-hosted. Cube Cloud adds managed infrastructure, monitoring, a dev environment, and enterprise security. It's a good fit for engineering-led teams building data products or multi-BI environments who want a headless, warehouse-agnostic layer. Non-technical analysts will find it less approachable, since everything is defined in code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Open-source core (Cube Core) allows self-hosting and avoids vendor lock-in.&lt;/li&gt;
&lt;li&gt;Built-in pre-aggregations and caching improve performance and reduce warehouse cost.&lt;/li&gt;
&lt;li&gt;Multiple APIs (SQL, REST, GraphQL) suit embedded analytics and custom apps.&lt;/li&gt;
&lt;li&gt;Warehouse-agnostic with multi-tenancy and fine-grained access control.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Developer-centric and code-first, so less approachable for non-technical analysts.&lt;/li&gt;
&lt;li&gt;Self-hosting Cube Core requires real infrastructure and ops effort.&lt;/li&gt;
&lt;li&gt;Modeling is separate from dbt, so teams need to keep definitions aligned.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Cube Core is free and open source. Cube Cloud offers a free tier for development and testing. Paid tiers (Premium and Enterprise) are usage-based and priced by compute and infrastructure, with custom enterprise quotes. Current rates are on cube.dev/pricing.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. AtScale
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq5h4n9hiwmig613lw17p.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq5h4n9hiwmig613lw17p.png" alt="AtScale" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;AtScale has been in the semantic layer space longer than most. It sits between cloud warehouses or lakehouses (Snowflake, Databricks, BigQuery, Redshift) and consumption tools like Excel, Power BI, Tableau, and Looker. Teams build a governed, multidimensional business model with shared metrics, hierarchies, and calculations, and business users can query it without moving data.&lt;/p&gt;

&lt;p&gt;The engine rewrites queries and manages aggregates automatically. That autonomous acceleration is one of its stronger differentiators compared to lighter semantic layers. SQL, MDX, and DAX access make it work especially well with Excel and Power BI, which is a big deal if your organization has a lot of finance and ops users living in those tools. AtScale also offers modeling-as-code through SML (Semantic Modeling Language), which is open-sourced, and ships integrations for AI and LLM apps.&lt;/p&gt;

&lt;p&gt;It targets large enterprises that run many BI tools and need consistent governance at scale, particularly those moving off legacy OLAP cubes. Expect a sales-led onboarding and a heavier implementation than lightweight tools.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Mature multidimensional modeling, hierarchies, and MDX/DAX support, which suits Excel and Power BI users.&lt;/li&gt;
&lt;li&gt;Autonomous aggregate management accelerates queries without manual tuning.&lt;/li&gt;
&lt;li&gt;Works across many BI tools and cloud data platforms with centralized governance.&lt;/li&gt;
&lt;li&gt;Open Semantic Modeling Language (SML) supports modeling as code and portability.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Enterprise-oriented, with heavier implementation and sales-led onboarding than lightweight tools.&lt;/li&gt;
&lt;li&gt;Pricing isn't published, which makes it harder for smaller teams to budget.&lt;/li&gt;
&lt;li&gt;Smaller developer community than open-source options like dbt and Cube.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Custom, quote-based enterprise pricing with no public price list or free tier. AtScale has also been available through cloud marketplaces and as a Snowflake-native option. Contact AtScale for a quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Looker (LookML)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fu78w6drajo661z8ahu07.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fu78w6drajo661z8ahu07.png" alt="Looker (LookML)" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Looker is Google Cloud's enterprise BI platform, and its core is LookML, a code-based modeling language where developers define dimensions, measures, joins, and business logic once in Git-versioned files. Every dashboard, explore, and API call is generated from that governed model. It queries data in place against BigQuery, Snowflake, Redshift, Databricks, and many other SQL databases, so there are no extracts to manage.&lt;/p&gt;

&lt;p&gt;Embedded analytics and API capabilities are strong, and Google has been adding Gemini-powered conversational analytics plus a Looker semantic layer connector for use with other tools such as Looker Studio and Google Sheets. If you're already on Google Cloud and want a governed semantic layer tightly coupled to a BI front end, Looker is a natural choice.&lt;/p&gt;

&lt;p&gt;The trade-off is that the semantic layer really wants to live inside the Looker ecosystem. LookML has a learning curve, and portability to other BI tools is more limited than with a neutral semantic-layer tool. It also tends to be expensive for smaller teams once you factor in platform fees and per-user licensing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Mature, Git-based modeling language (LookML) with strong governance and version control.&lt;/li&gt;
&lt;li&gt;Powerful embedded analytics and API options for customer-facing products.&lt;/li&gt;
&lt;li&gt;Queries data in place without extracts, with deep Google Cloud and BigQuery integration.&lt;/li&gt;
&lt;li&gt;Growing AI and conversational analytics features that sit on the governed model.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;LookML has a learning curve and ties the semantic layer to Looker, limiting portability to other BI tools.&lt;/li&gt;
&lt;li&gt;Expensive for smaller teams, with platform fees plus per-user licensing.&lt;/li&gt;
&lt;li&gt;Less suited to a neutral, tool-agnostic semantic layer than dbt, Cube, or AtScale.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Custom, quote-based pricing through Google Cloud sales. It generally combines a platform fee with per-user licenses (Viewer, Standard, Developer). Third-party sources have reported platform fees starting around $35,000 a year and higher, which I couldn't verify, so get a current quote from Google. Looker Studio is separate, with a free tier and a paid Pro tier.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Snowflake Semantic Views
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnyvzhivx0bj0s775rjsx.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnyvzhivx0bj0s775rjsx.png" alt="Snowflake Semantic Views" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Semantic Views are Snowflake's native way to define a semantic layer inside the database. You define logical tables, relationships, dimensions, facts, and metrics as a schema-level object. You can query them with plain SQL and use them to ground Cortex Analyst, Snowflake's natural-language-to-SQL feature, in governed business definitions.&lt;/p&gt;

&lt;p&gt;Because the semantic model lives in Snowflake, it inherits Snowflake's RBAC, governance, and performance, and you don't need a separate server or API layer. Snowflake has also been promoting an open semantic interchange initiative with partners, including dbt Labs and BI vendors, aimed at making semantic definitions portable across tools.&lt;/p&gt;

&lt;p&gt;If your organization is heavily standardized on Snowflake and you want a low-overhead semantic foundation for BI and AI agents, this is a solid option. The obvious limitation is that it only covers Snowflake data, so it's not a cross-platform choice. It's also newer and less feature-rich than dedicated platforms when it comes to acceleration, multidimensional modeling, and MDX/DAX support.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Native to Snowflake, so no extra infrastructure and it reuses existing RBAC and governance.&lt;/li&gt;
&lt;li&gt;Directly grounds Cortex Analyst and other AI features in governed definitions.&lt;/li&gt;
&lt;li&gt;Queryable with plain SQL and increasingly supported by BI tools and partners.&lt;/li&gt;
&lt;li&gt;No separate license for the semantic layer itself.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Snowflake-only, so it doesn't work as a universal layer across Databricks, BigQuery, and others.&lt;/li&gt;
&lt;li&gt;Newer and less feature-rich than dedicated platforms (acceleration, multidimensional modeling, MDX/DAX).&lt;/li&gt;
&lt;li&gt;Usage runs on Snowflake compute credits, so costs scale with queries and AI usage.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; No separate license fee for Semantic Views. Costs come from Snowflake's consumption-based pricing (compute credits for queries, plus credits for Cortex AI features). Total cost depends on your Snowflake edition, region, and contract.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Verdict
&lt;/h2&gt;

&lt;p&gt;If you only read the first paragraph of this article, here's the summary: the semantic layer is really two problems that most tools treat as one. Problem one is defining business metrics in a governed way. Problem two is keeping those definitions aligned with the actual physical schema in the warehouse underneath. Every tool here solves the first problem. Only SqlDBM solves both, which is why it's my pick for best overall.&lt;/p&gt;

&lt;p&gt;If you already live in dbt and just want metrics in YAML next to your models, the dbt Semantic Layer is a reasonable fit. If you're building embedded or customer-facing analytics and need caching, Cube is strong. If you're a large enterprise still running Excel and Power BI heavily, AtScale earns its keep. If you're all-in on Looker, LookML already is your semantic layer. And if your stack is 100% Snowflake and you want AI grounding with no new infrastructure, Semantic Views are good enough.&lt;/p&gt;

&lt;p&gt;For everyone else, especially teams that are also doing serious data modeling work and want AI agents and BI tools pulling from the same governed source of truth, SqlDBM is the one I'd start with.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What is a semantic layer and why does it matter in 2026?&lt;/strong&gt;&lt;br&gt;
A semantic layer is a governed translation between raw warehouse tables and business concepts like "revenue" or "active customer." It matters more now because AI agents and LLMs need consistent definitions to answer business questions without hallucinating, and because BI sprawl has made conflicting metrics a bigger problem than ever.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I use SqlDBM alongside dbt or Cube?&lt;/strong&gt;&lt;br&gt;
Yes. SqlDBM generates dbt-compatible YAML directly from the visual model, so it slots in as the modeling and governance layer upstream of dbt. Teams using Cube or other downstream tools can still rely on SqlDBM to keep the physical and semantic definitions in sync.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need a semantic layer if I already use Looker or Power BI?&lt;/strong&gt;&lt;br&gt;
Not strictly, since both have their own modeling features. But if you use multiple BI tools, or want to serve metrics to AI agents, embedded apps, or notebooks, a dedicated semantic layer prevents each tool from defining metrics its own way.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which tool is cheapest to start with?&lt;/strong&gt;&lt;br&gt;
Cube Core is free and open source if you're willing to self-host. Snowflake Semantic Views have no separate license fee if you're already on Snowflake. SqlDBM also has a free tier for exploring and modeling before you commit to a paid plan.&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>data</category>
      <category>tools</category>
    </item>
    <item>
      <title>Best Databricks Data Modeling Tools (2026): SQLDBM, dbt, SQLMesh, ER/Studio &amp; Hackolade Compared</title>
      <dc:creator>Dainius Remeika</dc:creator>
      <pubDate>Thu, 15 Oct 2026 14:56:38 +0000</pubDate>
      <link>https://dev.to/danremake/best-databricks-data-modeling-tools-2026-sqldbm-dbt-sqlmesh-erstudio-hackolade-compared-4612</link>
      <guid>https://dev.to/danremake/best-databricks-data-modeling-tools-2026-sqldbm-dbt-sqlmesh-erstudio-hackolade-compared-4612</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F854d9vhu7ay40audv0z2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F854d9vhu7ay40audv0z2.png" alt="header" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Databricks has become the default lakehouse for a huge chunk of serious data teams, and the modeling tools around it have had to grow up fast. Unity Catalog, Delta Lake, column-level lineage, dbt-style transformations, semantic layers for AI and BI, it's all happening at once. Picking the right modeling tool in 2026 isn't just about pretty ERDs anymore. It's about which tool actually plugs into your Databricks workflow without fighting you.&lt;/p&gt;

&lt;p&gt;I spent weeks working through the main contenders, from browser-based visual tools to code-first transformation frameworks to the old-guard desktop modelers. Some are genuinely built for the lakehouse. Others bolted on Databricks support later and it shows. A few don't even try to be visual, and that's fine, they solve a different problem.&lt;/p&gt;

&lt;p&gt;Here's the short list I ended up with, and how each one actually performs when you point it at a Databricks environment.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Evaluated These Tools
&lt;/h2&gt;

&lt;p&gt;I focused on five things: depth of Databricks and Unity Catalog integration, support for conceptual/logical/physical modeling (versus pure code transformation), collaboration and Git/CI workflows, enterprise features like governance and SSO, and pricing transparency. I also weighed how well each tool handles the newer stuff teams actually care about now, semantic layers, AI assistance, and tags.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. SqlDBM - Best Overall
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" alt="SqlDBM" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The only visual modeling platform that natively speaks Databricks, from Unity Catalog to semantic layer to production DDL.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;After spending real time with every tool on this list, I keep coming back to SqlDBM as the most complete option for teams building on the Databricks Lakehouse. It's cloud-native and browser-based. No desktop installs, no license servers, no VM to babysit. And the Databricks integration goes genuinely deep.&lt;/p&gt;

&lt;p&gt;SqlDBM is a &lt;strong&gt;Databricks Validated Data Partner&lt;/strong&gt;, and that partnership shows up in the product. It connects directly to Unity Catalog and Hive Metastore, with native reverse and forward engineering against Delta Lake objects, column-level lineage, and the ability to visually model everything from conceptual designs to physical schemas without writing a line of code. In 2026 they added Databricks tags support, so you can organize, classify, and search Unity Catalog schemas, tables, views, and columns right inside your model, and keep everything synced through forward and reverse engineering. Transformational alter scripts for Databricks also landed recently, which rounds out the CI/CD story nicely.&lt;/p&gt;

&lt;p&gt;What really sets SqlDBM apart is scope. It's the first platform to combine relational and transformational (Tx) modeling in one workspace, so you can design gold-layer tables alongside dbt-style transformation logic, then push dbt source and model YAML straight through Git. On top of that, its semantic modeling layer lets you define governed business definitions directly on top of physical Databricks schemas. Standalone semantic tools like dbt's Semantic Layer or Cube skip the visual modeling side entirely. Visual tools like ER/Studio and Hackolade skip the semantic layer. SqlDBM bridges both.&lt;/p&gt;

&lt;p&gt;The proof is in production. John Holland Group, one of Australia's largest infrastructure firms, completed its Databricks migration in nine months using SqlDBM as the authoritative source for gold-layer models. FrieslandCampina's data modeling lead said SqlDBM "fundamentally streamlined" their Databricks modeling process. Over 400,000 users trust the platform, including DocuSign, Pfizer, and Sophos. PwC reported it cuts modeling time by 25 percent, and it won Database Modeling Solution of the Year in both 2023 and 2024.&lt;/p&gt;

&lt;p&gt;The built-in AI Copilot and MCP Server, announced live at Databricks Data + AI Summit 2025, make models directly accessible to LLMs. That's a huge edge for teams building AI-ready Lakehouse architectures. Real-time multi-user collaboration means architects, engineers, and analysts all work concurrently in the same model. Enterprise security (SSO, RBAC, SOC 2 Type II) checks every box.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deepest native Databricks integration of any visual modeling tool: Unity Catalog direct connect, Delta Lake forward/reverse engineering, Databricks tags, transformational alter scripts, and column-level lineage all built in&lt;/li&gt;
&lt;li&gt;Only visual data modeling platform that also delivers a semantic layer for Databricks, bridging governed physical schemas and business definitions where dbt, ER/Studio, and Hackolade each cover only one side&lt;/li&gt;
&lt;li&gt;First platform combining relational and transformational (Tx) modeling, so you design gold-layer Databricks tables and push dbt source/model YAML through Git and CI/CD in one workspace&lt;/li&gt;
&lt;li&gt;Proven at scale: John Holland Group completed a Databricks migration in nine months with SqlDBM governing gold-layer models, and PwC reports 25% faster modeling time&lt;/li&gt;
&lt;li&gt;AI Copilot and MCP Server expose Databricks models directly to LLMs, a tangible edge for AI-ready Lakehouse architectures&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Advanced features like semantic modeling and Tx modeling have a learning curve for teams new to visual modeling&lt;/li&gt;
&lt;li&gt;Databricks, Snowflake, and BigQuery coverage is deep, but support for niche or on-prem databases is narrower than legacy desktop tools&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; SqlDBM plans are quote-based and scale with team size, with enterprise packaging, premium support, and advanced security options available. There's a free tier so you can model and explore before committing. Contact sales for a tailored quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. dbt (dbt Core / dbt platform)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3axgw44nzikrj1unj5h2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3axgw44nzikrj1unj5h2.png" alt="dbt (dbt Core / dbt platform)" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;dbt is the analytics-engineering standard for transforming data inside the warehouse or lakehouse. Teams write modular SQL (or Python) models, and dbt handles dependency ordering, materialization, testing, documentation, and lineage. The Databricks adapter is mature, so models run cleanly on Databricks SQL and Unity Catalog. The free, open-source dbt Core runs locally or in your own orchestrator. The commercial dbt platform (formerly dbt Cloud) adds a browser IDE, scheduling, CI, a catalog, a Semantic Layer, and AI assistance.&lt;/p&gt;

&lt;p&gt;One thing to be clear about: dbt is not a visual ERD or conceptual/logical modeling tool. It models transformation logic in code. So it usually complements a design tool like SqlDBM, ER/Studio, or Hackolade rather than replacing one. It fits data and analytics engineers who want Git-based workflows, code review, and automated testing for transformation pipelines. The community and package ecosystem are huge. Sources indicate dbt Labs has become part of Fivetran, which is worth confirming for roadmap and licensing questions.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Huge community, package ecosystem, and broad hiring pool&lt;/li&gt;
&lt;li&gt;Mature Databricks adapter with built-in testing, documentation, and lineage&lt;/li&gt;
&lt;li&gt;Free open-source core with Git/CI-friendly workflows&lt;/li&gt;
&lt;li&gt;Semantic Layer and catalog features on the paid platform&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No visual ERD, conceptual, or logical modeling, it only covers the transformation layer&lt;/li&gt;
&lt;li&gt;Paid platform costs scale with seats and successful model builds, Enterprise pricing is quote-only&lt;/li&gt;
&lt;li&gt;Requires SQL/Jinja and engineering skills, so it is less accessible to architects and business users&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; dbt Core is free (Apache 2.0). The dbt platform has a free Developer plan for 1 seat, Starter at about $100 per user per month, and negotiated Enterprise and Enterprise+ tiers. Usage overages apply, and Databricks compute is billed separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. SQLMesh (Tobiko Data)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5ffp2pb3nm7dc38nm7rc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5ffp2pb3nm7dc38nm7rc.png" alt="SQLMesh (Tobiko Data)" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SQLMesh is an open-source framework from Tobiko Data for building, testing, and deploying SQL and Python data pipelines. It's built on SQLGlot, which parses SQL semantically and can transpile across 20+ dialects. Databricks is a supported engine. The main differentiators are virtual data environments, plan/apply change workflows that show the impact of a change before it runs, automatic breaking-change detection, built-in unit tests, and column-level lineage. Because it tracks state, it can avoid unnecessary rebuilds, which can cut compute spend on Databricks meaningfully.&lt;/p&gt;

&lt;p&gt;It also has a VS Code extension and can run against existing dbt projects. Tobiko Cloud is the commercial layer, adding collaboration, observability, and cost tracking. Like dbt, SQLMesh is a transformation and model-management tool, not a visual ERD designer. It fits teams that want code-first modeling with stronger DataOps safeguards rather than diagramming and governance of conceptual and logical models.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Virtual environments and plan/apply workflow reduce rebuilds and warehouse cost&lt;/li&gt;
&lt;li&gt;Column-level lineage and semantic SQL understanding via SQLGlot&lt;/li&gt;
&lt;li&gt;Open-source core under Apache 2.0, with dbt project compatibility&lt;/li&gt;
&lt;li&gt;Native Python support and a VS Code extension&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Much smaller community and ecosystem than dbt&lt;/li&gt;
&lt;li&gt;Tobiko Cloud pricing is not published and requires talking to sales&lt;/li&gt;
&lt;li&gt;No visual ERD or conceptual/logical modeling, and a steeper learning curve for teams already on dbt&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; SQLMesh core is free and open source. Tobiko Cloud pricing is custom and the vendor does not publish it. Databricks compute costs are separate.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. ER/Studio Data Architect
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9c0nuwcg2f7gj7dgovj1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9c0nuwcg2f7gj7dgovj1.png" alt="ER/Studio Data Architect" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;ER/Studio Data Architect is a long-established enterprise modeling product, now offered through IDERA and Precisely. It supports conceptual, logical, and physical models, forward and reverse engineering, model comparison, impact analysis, naming standards, and macros for automation. Databricks support arrived in version 20.2, alongside SQL Server, Oracle, PostgreSQL, Snowflake, and others. Newer releases add an AI modeling assistant that can generate logical models from text prompts. It integrates with governance tools like Collibra and Microsoft Purview, and supports Okta SSO.&lt;/p&gt;

&lt;p&gt;This is a desktop-centric tool aimed at large enterprises and regulated industries with multi-platform estates and formal data-governance requirements. If that's your world, it has the depth you'd expect. Teams that want a lightweight, browser-first, or Git-native experience may find it heavier than newer cloud-native tools. The core audience is users who need broad legacy-database coverage and enterprise repository features.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deep enterprise feature set including model comparison, impact analysis, and standards enforcement&lt;/li&gt;
&lt;li&gt;Supports Databricks alongside many legacy and cloud databases&lt;/li&gt;
&lt;li&gt;Integrations with governance and catalog tools such as Collibra and Microsoft Purview&lt;/li&gt;
&lt;li&gt;AI-assisted model generation in recent versions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Higher per-user cost than most competitors&lt;/li&gt;
&lt;li&gt;Desktop-first architecture feels less collaborative than cloud-native tools&lt;/li&gt;
&lt;li&gt;Databricks support was added relatively recently and may be less deep than tools built around Unity Catalog&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Subscription pricing starts at about $2,687 per user per year for Standard, with Professional at about $3,693 per user and Enterprise on custom quote. A free trial is available, and reseller listings show a perpetual multiplatform license at about $2,674.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Hackolade Studio
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fia68udhagk6xjhnqhew0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fia68udhagk6xjhnqhew0.png" alt="Hackolade Studio" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hackolade Studio started as a visual modeling tool for NoSQL databases and has grown into a polyglot modeling platform covering 45+ targets, from Oracle and Databricks to MongoDB, Avro, and OpenAPI. For Databricks, it has dedicated Delta Lake support, including Unity Catalog. It models catalogs, schemas, tables, and views, forward-engineers scripts, reverse-engineers existing structures (including from a live Databricks instance), compares models, and generates documentation. It also has a CLI for CI/CD pipelines and Git integration.&lt;/p&gt;

&lt;p&gt;The idea is that you define meaning once in a technology-agnostic model, then derive physical schemas for each platform. That suits organizations that mix lakehouse, NoSQL, streaming, and API data. Hackolade is offered as a desktop application and as a browser-based deployment, and there's a free Community edition. The interface and workflow are less conventional than classic ERD tools, and collaboration leans on Git rather than live multi-user editing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Very broad technology coverage across SQL, NoSQL, APIs, and streaming formats&lt;/li&gt;
&lt;li&gt;Dedicated Databricks Delta Lake and Unity Catalog support with forward and reverse engineering&lt;/li&gt;
&lt;li&gt;Git integration and CLI for CI/CD automation&lt;/li&gt;
&lt;li&gt;Free Community edition and a transparent price list&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Collaboration is Git-based rather than real-time multi-user editing&lt;/li&gt;
&lt;li&gt;Polyglot, schema-centric paradigm has a learning curve for traditional ERD users&lt;/li&gt;
&lt;li&gt;Some advanced features sit behind paid editions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Free 14-day trial and a free Community edition. Paid subscriptions are listed at about €175 per seat per month or €1,750 per seat per year, including support. Volume and enterprise purchasing is available through sales.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. erwin Data Modeler (Quest)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa5kh1y3px5j86w09vktz.JPG" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa5kh1y3px5j86w09vktz.JPG" alt=" " width="800" height="373"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;erwin Data Modeler, from Quest Software, is one of the best-known enterprise data modeling tools. It supports forward and reverse engineering of database schemas, a centralized model repository, collaborative modeling with conflict resolution, change management, and auditing. It covers traditional relational platforms along with modern cloud targets like Databricks, Snowflake, and Microsoft Fabric. It's aimed at large enterprises with regulated, multi-platform environments and established governance processes.&lt;/p&gt;

&lt;p&gt;Users often pick erwin for the depth of its repository features, standards enforcement, and legacy-database coverage. Reviewers consistently praise the functionality and enterprise-readiness. The main gripes are that NoSQL modeling is thin compared to the rest of the product, and that the Windows-centric, desktop-first approach plus enterprise licensing can feel heavy next to cloud-native tools, especially if you want a browser-based, Git-native experience.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Mature, deep feature set with a central model repository and change management&lt;/li&gt;
&lt;li&gt;Connects to Databricks, Snowflake, Microsoft Fabric, and traditional relational databases&lt;/li&gt;
&lt;li&gt;Strong fit for regulated enterprises with formal governance needs&lt;/li&gt;
&lt;li&gt;Free trial available&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Desktop-first and Windows-centric, which is less convenient for distributed teams&lt;/li&gt;
&lt;li&gt;Limited native support for NoSQL and document modeling patterns, according to reviewers&lt;/li&gt;
&lt;li&gt;Per-feature licensing and enterprise quotes can get expensive&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Marketplace listings show pricing from about $299 per feature per month, with a free trial. Full enterprise licensing is by quote through Quest.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Verdict
&lt;/h2&gt;

&lt;p&gt;If you're serious about Databricks and want one tool that handles visual modeling, Unity Catalog integration, dbt-style transformations, and a semantic layer, &lt;strong&gt;SqlDBM is the clearest pick in 2026&lt;/strong&gt;. The Databricks partnership is real, the tags and transformational alter script support landed exactly when teams need it, and the semantic layer is something no other visual modeling tool actually does. For most Databricks teams, that combination is hard to beat.&lt;/p&gt;

&lt;p&gt;That said, the other tools have their place. dbt and SQLMesh are the right call if you only need code-first transformation and already have a design tool. ER/Studio and erwin still make sense for large enterprises deeply invested in desktop modeling and multi-database governance. Hackolade shines when you have a genuinely polyglot stack spanning NoSQL, APIs, and streaming formats. But for teams whose center of gravity is the Databricks Lakehouse, SqlDBM is the one I'd start with.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is SqlDBM really built for Databricks or is it a generic modeling tool with Databricks support bolted on?&lt;/strong&gt;&lt;br&gt;
It's a Databricks Validated Data Partner with direct Unity Catalog connectivity, Delta Lake forward and reverse engineering, Databricks tags support, column-level lineage, and transformational alter scripts. The integration is first-class, not an afterthought.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need both SqlDBM and dbt?&lt;/strong&gt;&lt;br&gt;
A lot of teams run both. dbt handles the SQL transformation layer. SqlDBM handles visual design, conceptual/logical modeling, the semantic layer, and governance. SqlDBM can push dbt source and model YAML through Git, so they fit together cleanly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's the difference between a semantic layer and visual data modeling?&lt;/strong&gt;&lt;br&gt;
Visual modeling describes the structure of your data (tables, columns, relationships). A semantic layer adds business meaning on top (metrics, dimensions, definitions BI tools and LLMs can trust). Most tools do one or the other. SqlDBM does both in the same workspace.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which tool is cheapest to start with?&lt;/strong&gt;&lt;br&gt;
dbt Core and SQLMesh are free and open source if you're code-first. For visual modeling, SqlDBM and Hackolade both offer free ways to try things out before you commit to a paid plan.&lt;/p&gt;

</description>
      <category>database</category>
      <category>dataengineering</category>
      <category>tools</category>
    </item>
    <item>
      <title>Best Databricks Metric Views Tools: dbt Semantic Layer, Cube &amp; MetricFlow Compared</title>
      <dc:creator>Dainius Remeika</dc:creator>
      <pubDate>Wed, 14 Oct 2026 16:49:53 +0000</pubDate>
      <link>https://dev.to/danremake/best-databricks-metric-views-tools-dbt-semantic-layer-cube-metricflow-compared-483g</link>
      <guid>https://dev.to/danremake/best-databricks-metric-views-tools-dbt-semantic-layer-cube-metricflow-compared-483g</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpb5m1ky54v9z4kk7qyfy.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpb5m1ky54v9z4kk7qyfy.png" alt="header" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Metric views are suddenly a big deal on Databricks. Unity Catalog now has a native way to define measures and dimensions as governed objects, and every semantic-layer vendor is racing to plug into it. That's great news if you're tired of three different dashboards reporting three different numbers for "active customers." It's also a bit of a mess, because the ecosystem splintered overnight.&lt;/p&gt;

&lt;p&gt;I spent time working through the main contenders: Databricks' own Metric Views, dbt's Semantic Layer, Cube, MetricFlow, AtScale, and a visual modeling platform called SqlDBM that solves a problem the others don't even acknowledge. If you've ever had a metric definition silently break because somebody renamed a column upstream, you already know what I mean.&lt;/p&gt;

&lt;p&gt;Below I've ranked them based on how well they actually help you ship trustworthy metrics on Databricks, not just define them in YAML.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Evaluated These Platforms
&lt;/h2&gt;

&lt;p&gt;I looked at native integration with Databricks and Unity Catalog, how well each tool handles the physical-to-semantic bridge (because metric views are only as good as the schemas underneath), performance features like caching and pre-aggregation, support for AI agents and MCP, pricing clarity, and the honest trade-offs each tool makes. I also weighed enterprise proof points and how each handles schema change over time, which is where most metric definitions quietly rot.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. SqlDBM - Best Overall
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" alt="SqlDBM" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The governed foundation your Databricks metric views are missing: visual modeling meets the semantic layer in one workspace.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When I started testing tools for Databricks metric views, I kept hitting the same wall. Standalone semantic-layer tools like dbt's Semantic Layer, Cube, and MetricFlow let you define metrics beautifully, but they have no idea what the physical schema underneath actually looks like. Rename a column, refactor a join, change a table, and your metric definitions silently break. That's the exact gap SqlDBM fills, and it's why I'm putting it at the top.&lt;/p&gt;

&lt;p&gt;SqlDBM is a cloud-native, code-free data modeling platform and a &lt;strong&gt;Databricks Validated Data Partner&lt;/strong&gt; that plugs directly into Unity Catalog. You can reverse- and forward-engineer Delta Lake objects, track column-level lineage, and visually govern every schema your metric views depend on. What makes it uniquely relevant here is the &lt;strong&gt;semantic modeling layer&lt;/strong&gt;. SqlDBM lets data teams define semantic views that layer business context onto physical warehouse schemas, giving BI tools, dbt models, and AI systems one governed definition of what your data actually means.&lt;/p&gt;

&lt;p&gt;Here's the key insight. Standalone semantic-layer tools (dbt, Cube, AtScale) skip visual modeling. Visual modeling tools (erwin, ER/Studio, Hackolade) skip the semantic layer. SqlDBM is the only platform that bridges both. It grounds semantic models in a governed physical foundation and automatically propagates schema changes so metric definitions stay accurate as your lakehouse evolves.&lt;/p&gt;

&lt;p&gt;The real-world Databricks proof is what sold me. John Holland Group, one of Australia's largest infrastructure firms, completed its Databricks cloud migration in nine months using SqlDBM as the authoritative source for gold-layer models. Mercadona, Spain's largest supermarket chain, governs nearly 5,000 tables in SqlDBM and uses the SqlDBM API to auto-generate dbt models. That's exactly the semantic-to-physical pipeline that makes metric views trustworthy at scale.&lt;/p&gt;

&lt;p&gt;With 400,000+ users globally, enterprise customers like DocuSign, Pfizer, and Zendesk, and back-to-back &lt;strong&gt;Database Modeling Solution of the Year&lt;/strong&gt; wins at the 2023 and 2024 Data Breakthrough Awards, the credibility is there. Real-time collaboration means multiple modelers can refine semantic definitions in parallel without stepping on each other.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Only visual modeling platform that bridges physical modeling and a semantic layer for Databricks, giving metric views, dbt models, and AI systems one governed definition while automatically propagating schema changes.&lt;/li&gt;
&lt;li&gt;Native Databricks Unity Catalog integration with full reverse/forward engineering and column-level lineage, so metric view definitions start from governed, documented schemas rather than guesswork.&lt;/li&gt;
&lt;li&gt;Enterprise-proven at Databricks scale: John Holland Group completed a nine-month Databricks migration with SqlDBM as the single source of truth, and Mercadona governs nearly 5,000 tables while auto-generating dbt models via the SqlDBM API.&lt;/li&gt;
&lt;li&gt;Real-time multi-user collaboration with branch-and-merge, so teams can define and refine semantic layers in parallel without conflicts.&lt;/li&gt;
&lt;li&gt;Databricks Validated Data Partner with an MCP Server that exposes governed models to LLMs, future-proofing metric views for AI agents and Genie.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Full semantic modeling capabilities live in the higher-tier Context Layer plan, so teams on the free tier will want to upgrade to unlock the complete metric-view governance workflow.&lt;/li&gt;
&lt;li&gt;If your stack is 100% code-first with zero visual modeling needs, the visual-first approach may feel like an extra step before the governance payoff kicks in.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; SqlDBM plans are quote-based and scale to team size, with enterprise packaging, premium support, and security options available. There's a free tier to start modeling and explore the platform before committing, no credit card required. Contact sales for a tailored quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Databricks Unity Catalog Metric Views
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk099jw6vuryhui57dncb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fk099jw6vuryhui57dncb.png" alt="Databricks Unity Catalog Metric Views" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Metric Views are Databricks' built-in way to define business metrics inside Unity Catalog. They separate measure definitions (revenue, active customers) from the dimensions used to group and filter them. You define metrics in YAML on top of a source table or view, and they get registered as governed Unity Catalog objects. That means they inherit the same permissions, lineage, and discoverability as every other UC asset.&lt;/p&gt;

&lt;p&gt;Once defined, the same metrics can be queried from Databricks SQL, AI/BI dashboards, alerts, Genie spaces, and external BI tools connected to Databricks. Because the metrics live in the lakehouse, there's no extra service to run and no data leaves the platform. For teams already all-in on Databricks, this is the lowest-friction option by a wide margin.&lt;/p&gt;

&lt;p&gt;The trade-off is portability. Definitions are tied to Databricks, and third-party docs still describe the feature as beta or public preview depending on the source. It also lacks the caching and pre-aggregation options that dedicated semantic platforms offer. Third parties like Cube and AtScale are building integrations that read from or publish into Metric Views, so you can combine approaches if needed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Native to Unity Catalog, so metrics inherit existing governance, permissions, and lineage.&lt;/li&gt;
&lt;li&gt;No separate infrastructure or vendor to buy; works directly with Databricks SQL, dashboards, and Genie.&lt;/li&gt;
&lt;li&gt;Defined once and reusable across BI, SQL, and AI/agent use cases.&lt;/li&gt;
&lt;li&gt;Third-party layers like Cube and AtScale are adding integrations, so it can complement other tools.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Definitions are tied to Databricks and not portable to other warehouses.&lt;/li&gt;
&lt;li&gt;Relatively new; some sources still describe it as preview/beta, and it requires a recent Databricks Runtime (16.4+ per community docs).&lt;/li&gt;
&lt;li&gt;Fewer downstream integrations and caching/pre-aggregation options than dedicated semantic-layer platforms.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; No separate license fee that I found. Metric Views are a Unity Catalog feature, and you pay standard Databricks compute (SQL warehouse/cluster) costs when querying them. Pricing follows your Databricks contract.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. dbt Semantic Layer
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fymgxnkpz5kjx85ddcwpn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fymgxnkpz5kjx85ddcwpn.png" alt="dbt Semantic Layer" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The dbt Semantic Layer lets teams define metrics centrally in YAML inside their dbt project, using the MetricFlow framework underneath. It then serves those metrics through APIs and integrations with downstream tools. It dynamically generates SQL to compute metrics on the fly, and offers first-class integrations with BI and analytics platforms.&lt;/p&gt;

&lt;p&gt;MetricFlow supports Snowflake, BigQuery, Databricks, Redshift, and Postgres (on dbt v1 only). That makes the Semantic Layer a solid fit for teams already modeling transformations in dbt who want their metric definitions version-controlled next to their models. It's part of the paid dbt platform (formerly dbt Cloud), and the free Developer plan doesn't include it.&lt;/p&gt;

&lt;p&gt;Compute still runs in your warehouse, so there's no dedicated pre-aggregation store. Latency depends on your Databricks SQL warehouse performance, and caching is Enterprise-tier only. Third-party comparisons also note that usage is metered by queried metrics, which can get costly at scale. It suits analytics engineering teams that want a vendor-neutral, code-first approach not tied to one warehouse.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Code-first metrics live in the same dbt project and Git workflow as your transformations.&lt;/li&gt;
&lt;li&gt;Works across several warehouses, including Databricks.&lt;/li&gt;
&lt;li&gt;Broad BI and tool integrations, with growing AI/MCP support.&lt;/li&gt;
&lt;li&gt;Backed by MetricFlow, which is now open source.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Requires a paid dbt platform plan; the free Developer plan excludes the Semantic Layer.&lt;/li&gt;
&lt;li&gt;No dedicated pre-aggregation or caching layer, so performance depends on the warehouse (caching is Enterprise-only).&lt;/li&gt;
&lt;li&gt;Metered queried-metrics limits and per-seat pricing can get expensive at scale.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; The dbt platform's Developer plan is free but excludes the Semantic Layer. The Starter plan is listed around $100 per user per month, and Enterprise/Enterprise+ are custom-quoted (figures reported by third-party comparison sites; confirm on dbt's pricing page).&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Cube (Cube Cloud / Cube Core)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faiilhik06h9i68ip63v0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faiilhik06h9i68ip63v0.png" alt="Cube (Cube Cloud / Cube Core)" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Cube is a headless semantic layer that connects to cloud warehouses and lakehouses, including Snowflake, Databricks, BigQuery, Redshift, and Postgres. Teams model metrics once, and Cube exposes them through SQL, REST, GraphQL, and MDX APIs, plus the Model Context Protocol (MCP) for AI agents. Unlike purely warehouse-side approaches, Cube includes caching and pre-aggregations (Cube Store) for faster queries. That matters for customer-facing and embedded analytics.&lt;/p&gt;

&lt;p&gt;Cube Core is open source under Apache 2.0, and Cube Cloud is the managed commercial platform. Cube Cloud adds a semantic-model IDE, workbooks and dashboards, AI agents, and enterprise security. Cube has also built a Databricks Metric View integration, currently in preview, that publishes selected Cube views as native Databricks Metric Views. It lets teams keep Cube as the modeling layer while exposing governed metrics inside Unity Catalog, though the integration needs to be activated through Cube support.&lt;/p&gt;

&lt;p&gt;Cube suits data engineering teams that want an independent, API-first layer with real performance features. The trade-off is operating another platform with its own modeling language.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Open-source Cube Core (Apache 2.0) plus a managed cloud option.&lt;/li&gt;
&lt;li&gt;Many APIs (SQL, REST, GraphQL, MDX) and MCP support for AI agents.&lt;/li&gt;
&lt;li&gt;Pre-aggregations and caching improve query performance and cost.&lt;/li&gt;
&lt;li&gt;Preview integration to publish Cube views as native Databricks Metric Views.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The Databricks Metric View publication is in preview and needs activation by Cube support, and some model features aren't supported (for example dynamic JavaScript/Jinja models).&lt;/li&gt;
&lt;li&gt;Another platform to learn and operate, with its own modeling language, alongside your warehouse.&lt;/li&gt;
&lt;li&gt;Cloud pricing combines per-seat and metered infrastructure costs, which can be hard to predict.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Cube Cloud has a free plan (five workbooks, 1,000 daily query requests). Starter is $40 per developer per month and Premium is $80 per developer per month, with Explorer seats at $40 and Viewer seats at $20. Enterprise is custom-priced. Cube Core is free and self-hosted (Apache 2.0). Figures are from third-party listings, so verify on Cube's pricing page.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. MetricFlow (open source)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqlj9y9doale46or0fynk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqlj9y9doale46or0fynk.png" alt="MetricFlow (open source)" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;MetricFlow is the semantic-layer engine from dbt Labs that compiles metric definitions into reusable SQL. It uses semantic model and metric YAML configurations to construct and run SQL against your data platform. dbt Labs acquired it through its 2023 acquisition of Transform.&lt;/p&gt;

&lt;p&gt;At Coalesce 2025, dbt Labs announced it was moving MetricFlow to the Apache 2.0 license (earlier versions, 0 to 0.140.0, were under AGPL). It was contributed as a reference implementation for the Open Semantic Interchange (OSI) effort. The docs state it works with Snowflake, BigQuery, Databricks, Postgres (dbt v1 only), and Redshift.&lt;/p&gt;

&lt;p&gt;Teams can use it directly or through the paid dbt Semantic Layer, which adds hosted APIs, BI integrations, and governance features. On its own, MetricFlow is a solid fit for engineering-led teams that want a free, code-first, portable way to define metrics and are comfortable running the infrastructure themselves. Just keep in mind it isn't a managed platform. The hosted APIs and many integrations belong to the paid dbt Semantic Layer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Free and open source under Apache 2.0.&lt;/li&gt;
&lt;li&gt;Portable metric definitions in YAML that live in Git.&lt;/li&gt;
&lt;li&gt;Works with Databricks and several other warehouses.&lt;/li&gt;
&lt;li&gt;Part of the Open Semantic Interchange effort, which aims at semantic portability.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The hosted APIs, caching, and many BI integrations require the paid dbt Semantic Layer.&lt;/li&gt;
&lt;li&gt;You run and maintain it yourself, and it needs dbt expertise.&lt;/li&gt;
&lt;li&gt;Not a native Databricks object, so metrics aren't governed in Unity Catalog the way Metric Views are.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Free to use under the Apache 2.0 license. The managed dbt Semantic Layer that builds on it requires a paid dbt platform plan (see dbt Semantic Layer).&lt;/p&gt;

&lt;h2&gt;
  
  
  6. AtScale
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq5h4n9hiwmig613lw17p.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq5h4n9hiwmig613lw17p.png" alt="AtScale" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;AtScale is a proprietary semantic-layer platform aimed at large enterprises. It integrates with Snowflake, Databricks, and Google BigQuery, and with tools like Tableau, Power BI, Excel, and Python. It acts as a governed semantic layer between the warehouse and consuming tools, so metrics are defined once and exposed consistently to BI users, data scientists, and AI agents.&lt;/p&gt;

&lt;p&gt;On Databricks, AtScale positions itself as part of a "semantic lakehouse" approach. It's a launch partner for Unity Catalog metrics and has announced bi-directional read and write with Unity Catalog metric definitions. It also offers an MCP server on the Databricks Marketplace to give AI agents access to governed metrics.&lt;/p&gt;

&lt;p&gt;AtScale is aimed at large organizations with many BI tools and multidimensional or Excel-heavy analytics needs. It's a stronger fit there than lighter, code-first options. Being a commercial enterprise product means a sales-led procurement process and, in most cases, maintaining a second set of metric definitions separate from your dbt or Databricks code.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Deep Databricks partnership, including Unity Catalog metric interoperability.&lt;/li&gt;
&lt;li&gt;Broad BI and analytics tool support (Tableau, Power BI, Excel, Python).&lt;/li&gt;
&lt;li&gt;Enterprise-oriented governance and an AI/MCP server for agents.&lt;/li&gt;
&lt;li&gt;Vendor-independent layer that isn't tied to a single warehouse.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Proprietary and sales-led, with no open-source core.&lt;/li&gt;
&lt;li&gt;Likely heavier to deploy and costlier than code-first options for small teams.&lt;/li&gt;
&lt;li&gt;Modeling is separate from your dbt or Databricks code, so teams may maintain a second set of definitions.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; I couldn't find public pricing. AtScale appears to be sold as a custom enterprise subscription, so contact AtScale for a quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Verdict
&lt;/h2&gt;

&lt;p&gt;If you're all-in on Databricks and want the simplest path, native Unity Catalog Metric Views are the obvious starting point. If you're a dbt shop that values code-first portability, the dbt Semantic Layer or MetricFlow make sense. Cube is the strongest pick for embedded analytics with real caching. AtScale is for enterprises with heavy BI and Excel footprints.&lt;/p&gt;

&lt;p&gt;But here's the thing none of those tools solve. Metric definitions are only trustworthy if the schemas underneath them are governed, documented, and don't silently change on you. That's why &lt;strong&gt;SqlDBM&lt;/strong&gt; is my top pick. It's the only platform I found that bridges visual physical modeling and a true semantic layer in one workspace, with native Databricks Unity Catalog integration, column-level lineage, and real-time collaboration. The customer stories at John Holland Group and Mercadona show it works at serious scale, and the MCP Server means your governed models are ready for the AI agent era.&lt;/p&gt;

&lt;p&gt;For most teams building metric views on Databricks, SqlDBM is the foundation that makes everything else on this list more reliable.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Can I use SqlDBM alongside Databricks Metric Views and dbt?&lt;/strong&gt;&lt;br&gt;
Yes. SqlDBM sits upstream as the governed modeling foundation. You can define semantic views in SqlDBM, publish schemas into Databricks via Unity Catalog, and even auto-generate dbt models through the SqlDBM API, which is exactly what Mercadona does.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Are Databricks Metric Views production-ready?&lt;/strong&gt;&lt;br&gt;
Depending on the source, Metric Views are described as public preview or beta and require Databricks Runtime 16.4+. Check Databricks' official docs for the current release status before standardizing on them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's the difference between MetricFlow and the dbt Semantic Layer?&lt;/strong&gt;&lt;br&gt;
MetricFlow is the open-source engine (Apache 2.0) that compiles YAML metric definitions into SQL. The dbt Semantic Layer is the paid managed service built on top of MetricFlow, adding hosted APIs, BI integrations, and governance features.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need a semantic layer if I already use Unity Catalog Metric Views?&lt;/strong&gt;&lt;br&gt;
Not necessarily. If you're Databricks-only and your BI needs are modest, native Metric Views may be enough. If you need multi-warehouse portability, pre-aggregation performance, or richer API access for embedded or AI use cases, a dedicated semantic layer like Cube or AtScale is worth considering, with SqlDBM providing the governed physical foundation underneath.&lt;/p&gt;

</description>
      <category>analytics</category>
      <category>data</category>
      <category>database</category>
    </item>
    <item>
      <title>Best Databricks AI Data Preparation Tools: Mosaic AI Vector Search &amp; Data Quality Solutions Compared</title>
      <dc:creator>Dainius Remeika</dc:creator>
      <pubDate>Tue, 13 Oct 2026 14:43:21 +0000</pubDate>
      <link>https://dev.to/danremake/best-databricks-ai-data-preparation-tools-mosaic-ai-vector-search-data-quality-solutions-compared-22lm</link>
      <guid>https://dev.to/danremake/best-databricks-ai-data-preparation-tools-mosaic-ai-vector-search-data-quality-solutions-compared-22lm</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7uae9v4yhkqlzm6iinh7.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7uae9v4yhkqlzm6iinh7.png" alt="header" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Every Databricks team I've worked with recently has run into the same problem. They want to ship RAG apps, agents, or semantic search on top of their lakehouse, and they assume the hard part is the vector database or the embedding model. It isn't. The hard part is making sure the data feeding those systems is governed, well-defined, and actually means what everyone thinks it means.&lt;/p&gt;

&lt;p&gt;That's why I spent a few weeks digging into the tools that sit around Mosaic AI Vector Search. Some of them prepare documents. Some monitor quality. Some index vectors. And one of them, in my opinion, does the quieter but more important work of making your schemas AI-ready in the first place.&lt;/p&gt;

&lt;p&gt;Below is my shortlist of five tools worth knowing if you're building AI workloads on Databricks, with honest notes on where each one fits.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Evaluated These Platforms
&lt;/h2&gt;

&lt;p&gt;I looked at native Databricks integration first, then considered how each tool actually improves AI output quality, how predictable the pricing is, and whether the vendor has real enterprise customers running the product at scale. I also paid attention to the gaps. A great vector index doesn't help you if the underlying metrics are defined three different ways, and a document parser doesn't help you if nobody governs the resulting tables.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. SqlDBM - Best Overall
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" alt="SqlDBM" width="799" height="562"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;The governed foundation that makes your Databricks lakehouse AI-ready before the first vector ever gets indexed.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When I started testing AI data preparation workflows on Databricks, I kept hitting the same wall. Mosaic AI Vector Search can retrieve content by similarity, but &lt;em&gt;similar&lt;/em&gt; isn't the same as &lt;em&gt;correct&lt;/em&gt;, especially when the same metric is defined three different ways across your warehouse. That's the gap &lt;a href="https://sqldbm.com/" rel="noopener noreferrer"&gt;SqlDBM&lt;/a&gt; fills, and it's why it sits at the top of this list.&lt;/p&gt;

&lt;p&gt;SqlDBM is a cloud-native, code-free data modeling platform that plugs directly into Databricks Unity Catalog and Hive Metastore. You can reverse- and forward-engineer Delta Lake objects, track column-level lineage, and visually govern every schema your AI pipelines depend on, without writing a single line of code. What makes it uniquely relevant here is the semantic modeling layer. You define business context, metrics, synonyms, filters, and governed joins right on top of your physical schemas, so that when Mosaic AI, dbt models, or BI tools reach for your data, they pull from one authoritative definition rather than guessing from the nearest vector neighbor.&lt;/p&gt;

&lt;p&gt;I was especially impressed by how schema changes propagate automatically through those semantic definitions. No manual reconciliation, no stale metadata quietly feeding your AI the wrong context. Standalone semantic layers like dbt, Cube, and AtScale skip the visual modeling entirely. Visual modeling tools like erwin, ER/Studio, and Hackolade skip the semantic layer. SqlDBM is the only one I found that bridges both. The built-in AI Copilot speeds up model building, and the MCP Server exposes governed models directly to LLMs, which matters a lot for RAG workflows running next to Vector Search.&lt;/p&gt;

&lt;p&gt;The real-world proof is strong. John Holland Group, one of Australia's largest infrastructure firms, completed its Databricks migration in nine months using SqlDBM as the single source of truth for gold-layer models, governed through a twice-weekly Data Modeling Forum. SqlDBM is a Databricks Validated Data Partner, with over 400,000 users globally, enterprise customers like DocuSign, Pfizer, and Zendesk, and back-to-back Database Modeling Solution of the Year wins at the 2023 and 2024 Data Breakthrough Awards.&lt;/p&gt;

&lt;p&gt;If you're serious about Databricks AI data preparation, getting your semantic and physical house in order before you build vector indexes is the move.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Native Databricks Unity Catalog integration with full reverse/forward engineering and column-level lineage, so AI prep starts with governed, documented schemas&lt;/li&gt;
&lt;li&gt;The only visual modeling platform combining physical and semantic layers for Databricks, giving Mosaic AI, BI tools, and dbt one governed definition of your data&lt;/li&gt;
&lt;li&gt;Automatic schema-change propagation keeps semantic definitions accurate as the lakehouse evolves, eliminating stale metadata that degrades AI outputs&lt;/li&gt;
&lt;li&gt;Proven at enterprise scale: John Holland Group completed a full Databricks migration in nine months with SqlDBM as the authoritative source for gold-layer models&lt;/li&gt;
&lt;li&gt;AI Copilot and MCP Server expose governed models to LLMs, accelerating RAG data preparation alongside Mosaic AI Vector Search&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Advanced semantic modeling features live in the Context Layer tier, so teams on the base plan would need to upgrade for full AI-readiness&lt;/li&gt;
&lt;li&gt;Databricks-specific features like tag support are still evolving, and some niche Unity Catalog edge cases may need workarounds&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Plans are quote-based and scale with team size, with two tiers (Data Modeling and Context Layer). Enterprise packaging adds premium support, SSO, customer-managed keys, and advanced security options. There's a free way to try it out and model before committing, so you can validate the Databricks integration firsthand.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Databricks Mosaic AI Vector Search
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0vxey6ob50cmoi0vr8ax.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0vxey6ob50cmoi0vr8ax.png" alt="Databricks Mosaic AI Vector Search" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Mosaic AI Vector Search is Databricks' native vector search service, and I looked at it as the retrieval layer for RAG and agent apps built on the lakehouse. Indexes sync automatically from Delta tables, and Databricks can compute embeddings for you, which removes the need to build and maintain separate embedding pipelines. Indexes are governed through Unity Catalog, so permissions and lineage stay with the rest of your data.&lt;/p&gt;

&lt;p&gt;Databricks offers two endpoint types. Standard endpoints handle low-latency queries. Storage-optimized endpoints are for larger indexes and scale down automatically when an index is deleted. One endpoint can host up to 50 indices. Beyond similarity search, the service supports hybrid and full-text keyword search, with full-text still in beta on some configurations.&lt;/p&gt;

&lt;p&gt;It fits teams already running on Databricks who want retrieval sitting next to their governed data without adding a third-party vector database. Worth knowing: this is a retrieval component, not a data cleaning tool. Chunking, parsing, and quality checks on the source data all have to be handled upstream.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Native Delta Sync indexes keep vectors current without custom pipelines&lt;/li&gt;
&lt;li&gt;Governed through Unity Catalog, so permissions and lineage stay unified&lt;/li&gt;
&lt;li&gt;Managed and serverless, no vector infrastructure to operate&lt;/li&gt;
&lt;li&gt;Both standard and storage-optimized endpoints, with up to 50 indices per endpoint&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Only useful inside the Databricks ecosystem, so lock-in is real&lt;/li&gt;
&lt;li&gt;Standard endpoints don't scale down automatically, so you keep paying for peak capacity until you manually recreate the endpoint&lt;/li&gt;
&lt;li&gt;Doesn't parse documents, chunk text, or validate data quality&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Pay-as-you-go through Databricks Units, no separate license. At GA on Azure, standard endpoints were around $0.28/hour per unit in eastus2 (2 million vectors per unit, 30 GB storage included, $0.23/GB/month beyond that). Rates vary by cloud and region, and storage-optimized endpoints have different pricing. Check current Databricks pricing for your region.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Unstructured
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhj6ond0tgapsf7rscuh0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhj6ond0tgapsf7rscuh0.png" alt="Unstructured" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Unstructured handles the document preparation step that comes before Vector Search. It ingests raw files, PDFs, Office docs, images, and scans, and partitions them into elements. From there it can chunk the content, optionally enrich it, generate embeddings, and write the output to a destination. Databricks Delta Tables (including Volumes) are a supported destination, so the output can feed a Mosaic AI Vector Search Delta Sync index directly.&lt;/p&gt;

&lt;p&gt;Processing strategies range from a fast text-only mode, to a High Res mode that combines document understanding with OCR, to a VLM mode that uses vision-language models for handwriting and complex scans. There are source connectors for systems like Google Drive. You can use the open-source library if you want to self-manage, or the hosted platform if you want workflows and connectors out of the box.&lt;/p&gt;

&lt;p&gt;It's aimed at ML and data engineers building RAG pipelines who'd rather not write brittle custom parsers. It handles unstructured documents, not tabular data quality monitoring, so you'd pair it with other tools in this list.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Handles many file types, with strategies for both simple and difficult documents (OCR and VLM)&lt;/li&gt;
&lt;li&gt;Supports Databricks Delta Tables as a destination, so output feeds Vector Search indexes&lt;/li&gt;
&lt;li&gt;Free starting allowance and simple per-page pricing&lt;/li&gt;
&lt;li&gt;Open-source library available alongside the hosted platform&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Focused on unstructured documents, so it doesn't monitor tabular data quality&lt;/li&gt;
&lt;li&gt;Per-page costs can add up on large archives, especially with advanced strategies&lt;/li&gt;
&lt;li&gt;An extra service to run alongside Databricks, with its own connectors and workflows&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Free tier with 10,000 pages and no credit card. Pay-as-you-go is $0.015 per page after that. Enterprise plans, including dedicated instance or VPC deployment, use custom pricing.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Soda
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff4wyn3pighih7dqcwahn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff4wyn3pighih7dqcwahn.png" alt="Soda" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Soda is a data quality and observability platform focused on testing, monitoring, and fixing data issues. Teams can embed checks at multiple points in CI/CD and data pipelines, which helps keep bad data out of production tables and the AI workloads that depend on them. It covers pipeline testing, metrics observability, alerting, and ticketing integrations. Higher tiers add collaborative data contracts, a no-code interface, and AI-powered quality features.&lt;/p&gt;

&lt;p&gt;Soda has a Databricks-focused offering and says it's built to scale on the platform. Users on G2 report that integrating it into an existing Databricks and Airflow stack was quick. Soda Core, the open-source project, is there for teams that want to write checks as code. Pricing is public and there's a genuinely free forever tier, which is refreshing in this category.&lt;/p&gt;

&lt;p&gt;It fits data engineering teams that want testing close to the pipeline and a path toward formal contracts between producers and consumers. It doesn't process documents or serve vectors, so it complements rather than replaces anything else on this list.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Public pricing and a free forever plan with unlimited users&lt;/li&gt;
&lt;li&gt;Checks embed in CI/CD and pipelines to catch problems before production&lt;/li&gt;
&lt;li&gt;Dedicated Databricks launch and integration, plus an open-source Soda Core option&lt;/li&gt;
&lt;li&gt;Enterprise tier adds data contracts, SSO, RBAC, audit logs, and private deployment&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The $750/month Team entry price is steep for small teams, and the free tier is limited to 3 production datasets&lt;/li&gt;
&lt;li&gt;Data contracts, no-code interface, and AI features are gated to the Enterprise tier&lt;/li&gt;
&lt;li&gt;Usage-based Soda Processing Units add cost variability as coverage grows&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Free: $0/month (up to 3 production datasets, pipeline testing, metrics observability, alerting, no credit card). Team: starts at $750/month, unlimited users, pay-as-you-go additional SPUs. Enterprise: custom pricing (data contracts, AI features, SSO, RBAC, private deployment). Annual billing and volume discounts available.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Monte Carlo
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxt9i8sbotp3yxtohf9wy.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxt9i8sbotp3yxtohf9wy.png" alt="Monte Carlo" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Monte Carlo is the enterprise end of the data observability category. It uses machine learning to identify anomalies, track freshness, and flag schema changes before they reach downstream reports or AI apps. Lineage and incident workflows are built in. It's available through Databricks Partner Connect with a 21-day free trial and usage-based pricing.&lt;/p&gt;

&lt;p&gt;Monte Carlo is known for fast time-to-value on standardized cloud stacks like Snowflake and dbt, and it supports Databricks as well. From what I found, it's best for mid-size to large organizations with many tables and multiple data teams that want automated, low-configuration monitoring. The out-of-the-box monitors cover volume and freshness, with custom rules on top. It's a monitoring layer on top of your data. It doesn't prepare documents or serve vectors, so it sits alongside tools like Unstructured and Mosaic AI Vector Search rather than replacing them.&lt;/p&gt;

&lt;p&gt;Pricing isn't published, and costs depend on monitored tables plus the compute your warehouse spends running checks. Small teams will likely find it overkill.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;ML-based anomaly detection with out-of-the-box freshness, volume, and schema monitors&lt;/li&gt;
&lt;li&gt;Available via Databricks Partner Connect with a 21-day free trial&lt;/li&gt;
&lt;li&gt;Strong lineage and incident-management features for large teams&lt;/li&gt;
&lt;li&gt;Established category leader with broad warehouse, lakehouse, and orchestration integrations&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;List pricing isn't published, and cost depends on monitored tables and usage&lt;/li&gt;
&lt;li&gt;Costs can become hard to predict at enterprise scale, and checks that query your warehouse add compute spend on top of the license&lt;/li&gt;
&lt;li&gt;Probably more than small teams or open-source-minded engineers need&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Usage-based with no public price list. Pricing depends on monitored tables, connected sources, and rules. Vendr reports an average contract value of roughly $62K (31 deals tracked). A 21-day free trial is available through Databricks Partner Connect. Contact sales for a quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Verdict
&lt;/h2&gt;

&lt;p&gt;If you build on Databricks and you're preparing data for AI, you'll likely end up using several of these tools together. Mosaic AI Vector Search handles retrieval. Unstructured chews through PDFs and scans. Soda or Monte Carlo watch for broken pipelines and anomalies.&lt;/p&gt;

&lt;p&gt;But none of those tools fix the deeper problem, which is that your AI pipelines are only as good as the definitions behind them. That's why SqlDBM is my pick for most teams starting this work. It's the one layer that makes the rest of the stack trustworthy. You get a governed physical model, a semantic layer that tells Mosaic AI and your BI tools what the data actually means, and automatic propagation so nothing goes stale. Build that foundation first, and every other tool on this list works better on top of it.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Do I need all of these tools to build RAG on Databricks?&lt;/strong&gt;&lt;br&gt;
No. At minimum you need vector retrieval (Mosaic AI Vector Search) and governed source data. Document parsing and observability tools are additions based on your use case. If you're mostly working with tabular data and well-modeled schemas, you may not need Unstructured at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where does SqlDBM fit if I already use dbt?&lt;/strong&gt;&lt;br&gt;
They complement each other. dbt transforms data. SqlDBM models and governs the schemas and semantic definitions those transformations target. The semantic layer in SqlDBM gives your dbt models and AI systems one shared, governed definition of each metric.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is Mosaic AI Vector Search enough on its own for a RAG app?&lt;/strong&gt;&lt;br&gt;
Only if your source data is already clean, chunked, and well-defined. Vector Search is retrieval, not preparation. You still need upstream tooling to handle documents and data quality.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How do Soda and Monte Carlo differ?&lt;/strong&gt;&lt;br&gt;
Soda is more developer- and pipeline-focused with public pricing and a free tier. Monte Carlo is heavier, more ML-driven, and aimed at larger organizations that want low-configuration monitoring across many tables.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>data</category>
      <category>llm</category>
      <category>rag</category>
    </item>
    <item>
      <title>Best dbt Data Modeling Tools for Documentation, Semantic Layer &amp; Migration</title>
      <dc:creator>Dainius Remeika</dc:creator>
      <pubDate>Mon, 12 Oct 2026 18:18:03 +0000</pubDate>
      <link>https://dev.to/danremake/best-dbt-data-modeling-tools-for-documentation-semantic-layer-migration-e41</link>
      <guid>https://dev.to/danremake/best-dbt-data-modeling-tools-for-documentation-semantic-layer-migration-e41</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff6c035otd6ocbbdz76yi.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ff6c035otd6ocbbdz76yi.png" alt="header" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;dbt is incredible at what it does. SQL transformations, tests, Git workflows, a growing package ecosystem. But if you've worked on a serious dbt project for any length of time, you know where the gaps are. There's no visual ERD. Documentation lives in YAML files that nobody wants to maintain. The semantic layer is tied to one project. And when you need to migrate legacy workloads into dbt, you're mostly on your own.&lt;/p&gt;

&lt;p&gt;So I spent time looking at the tools dbt teams actually reach for to fill those gaps. Some focus on visual modeling and documentation. Some are built for semantic metrics. Some exist specifically to automate migrations. A few try to span more than one of those categories.&lt;/p&gt;

&lt;p&gt;Below are the six tools I think are worth knowing about, with honest notes on what each one actually does and who it fits.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Evaluated These Tools
&lt;/h2&gt;

&lt;p&gt;I looked at four things: how well the tool complements a real dbt workflow (YAML generation, Git, lineage), how it handles documentation and discoverability, whether it offers a governed semantic layer, and how it holds up for migration work at enterprise scale. I weighted practical dbt integration heavily, because a tool that doesn't play nicely with dbt isn't useful to a dbt team.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. SqlDBM - Best Overall
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" alt="SqlDBM" width="799" height="562"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;The only visual modeling platform that gives dbt teams a governed semantic layer, migration-ready documentation, and production YAML in one workspace.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I've tested a lot of tools that claim to complement dbt, and SqlDBM is the one that genuinely fills the gaps dbt leaves open. Visual modeling, governed documentation, a semantic layer, and migration support, all without pulling you out of dbt's workflow.&lt;/p&gt;

&lt;p&gt;The dbt integration here is deep and production-grade. SqlDBM generates dbt source and model YAML directly from your visual models, now defaulting to the latest Fusion format, and pushes it straight to Git so your CI/CD pipelines stay in sync. You can also upload your dbt manifest to unify your ERD and DAG into a single view, with full upstream lineage that dbt's native DAG doesn't show. That alone solved a blind spot I kept running into on standalone dbt projects.&lt;/p&gt;

&lt;p&gt;What really sets SqlDBM apart is the semantic layer. It's the only visual modeling platform that bridges physical modeling and semantic definitions in one workspace. You define governed semantic views on top of your warehouse schemas, and when schemas change, those definitions propagate automatically. Your BI tools, dbt models, and AI systems all reference one trusted meaning. Standalone semantic tools like dbt's metrics layer or Cube skip visual modeling. Traditional modeling tools like erwin skip the semantic layer. SqlDBM does both.&lt;/p&gt;

&lt;p&gt;On migration, this is battle-tested at enterprise scale. John Holland Group, one of Australia's largest infrastructure firms, completed its Databricks migration in nine months using SqlDBM as the authoritative source for gold-layer models. Mercadona, Spain's largest supermarket chain, governs nearly 5,000 tables in SqlDBM and uses its API to auto-generate dbt models deployed to BigQuery. Les Mills manages 1,000+ Snowflake tables through it after explicitly rejecting erwin on usability grounds.&lt;/p&gt;

&lt;p&gt;With 400,000+ users globally, customers like DocuSign, Sophos, and Pfizer, and the Database Modeling Solution of the Year award two years running, the credibility is there. PwC reported a 25% reduction in modeling time, which tracked with my own experience. SqlDBM is also a Snowflake Premier Partner, Databricks Validated Data Partner, and Google Cloud Partner, so the native integrations across all three are first-class.&lt;/p&gt;

&lt;p&gt;If your team lives in dbt and needs visual modeling, governed documentation, a semantic layer, or migration tooling around it, SqlDBM is the clear pick.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Native dbt YAML generation (Fusion and Legacy formats) with Git push and CI/CD integration, plus dbt manifest import that unifies your ERD and DAG with full upstream lineage&lt;/li&gt;
&lt;li&gt;The only visual modeling platform with a governed semantic layer, so dbt models, BI tools, and AI systems share one trusted definition that auto-propagates schema changes&lt;/li&gt;
&lt;li&gt;Proven at enterprise migration scale: John Holland completed a Databricks migration in nine months; Mercadona governs nearly 5,000 tables and auto-generates dbt models via the SqlDBM API to BigQuery&lt;/li&gt;
&lt;li&gt;Real-time multi-user collaboration with branch-and-merge for semantic models, so multiple modelers can work on dbt documentation and semantic definitions in parallel without overwriting each other&lt;/li&gt;
&lt;li&gt;Cross-platform native integrations with Snowflake, Databricks (Unity Catalog), and BigQuery as a validated partner on all three, covering the most common dbt deployment targets&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Advanced features like Global Modeling and the semantic layer have a learning curve for teams new to governed, multi-project workflows&lt;/li&gt;
&lt;li&gt;dbt manifest import currently requires a manual upload or API call rather than a live sync. Functional, but a direct pipeline connection would be nice&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; SqlDBM has a free tier so you can start modeling and experiment with dbt YAML generation before committing. Beyond that, plans are quote-based and scale with team size, with enterprise packaging, premium support, and security options available. Contact sales for a tailored quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. dbt (dbt Cloud / dbt platform)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3axgw44nzikrj1unj5h2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3axgw44nzikrj1unj5h2.png" alt="dbt (dbt Cloud / dbt platform)" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;dbt is the obvious starting point for this list because it's the thing everything else here orbits around. The open-source framework handles version-controlled, tested SQL transformations in the warehouse. The managed dbt platform (formerly dbt Cloud) layers on a browser IDE, job scheduling, CI, and dbt Catalog for auto-generated documentation and lineage.&lt;/p&gt;

&lt;p&gt;Its Semantic Layer, powered by MetricFlow, lets teams define metrics once in code and serve them to BI tools through APIs. dbt is also a common migration target. Many teams move legacy SQL, stored procedures, or other ETL logic into dbt projects to get testing, documentation, and Git workflows.&lt;/p&gt;

&lt;p&gt;The thing to be honest about: dbt is not a visual modeling tool. You describe models in SQL and YAML, which suits analytics engineers more than business stakeholders. Teams often pair it with a diagramming or modeling tool like SqlDBM to design schemas before building. Column-level lineage and multi-project lineage (dbt Mesh) are gated to Enterprise, and the hosted Semantic Layer APIs need a paid plan.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Industry-standard framework with a huge community, package ecosystem, and wide warehouse support&lt;/li&gt;
&lt;li&gt;Documentation and lineage generated from code and kept current through dbt Catalog&lt;/li&gt;
&lt;li&gt;MetricFlow Semantic Layer centralizes metric definitions next to the transformation logic&lt;/li&gt;
&lt;li&gt;Free open-source dbt Core and a free single-seat Developer tier let teams start at no cost&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Code-first approach, with no visual ERD or conceptual/logical modeling&lt;/li&gt;
&lt;li&gt;Per-seat pricing plus usage charges (models built, queried metrics) can climb quickly&lt;/li&gt;
&lt;li&gt;Column-level lineage and multi-project features are Enterprise-only&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; dbt Core is free and open source. The managed platform has a free Developer plan (one seat). The Starter plan is around $100 per developer per month for up to five seats, including 15,000 models and basic Semantic Layer access. Enterprise tiers use custom pricing and often add per-queried-metric charges. Third-party estimates put 20-user deployments near $95K per year, but those figures are illustrative and negotiated.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Datafold
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fgenturascreenshots.s3.amazonaws.com%2Fscreenshots%2Flibrary%2F08009694-1864-4637-b817-10d995ff5061%2Fdatafold.com-316556f529ad8bd6.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fgenturascreenshots.s3.amazonaws.com%2Fscreenshots%2Flibrary%2F08009694-1864-4637-b817-10d995ff5061%2Fdatafold.com-316556f529ad8bd6.png" alt="Datafold" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Datafold is a data reliability platform best known for Data Diff, which compares datasets across environments and across databases. Its Data Migration Agent (DMA) combines AI-driven SQL translation with iterative, value-level validation, aimed at teams moving legacy SQL, stored procedures, or warehouse workloads into dbt on a modern platform.&lt;/p&gt;

&lt;p&gt;What's interesting about Datafold is the packaging. They sell migration as a fully translated, validated set of dbt models, delivered on a guaranteed timeline at a fixed price. Pricing depends on model count and complexity, not time and materials. Teams that prefer to run migrations themselves can use ad-hoc cross-database diffing just for validation.&lt;/p&gt;

&lt;p&gt;Datafold also provides CI/CD diffing for dbt pull requests, so you can see the data impact of a change before merging. It fits enterprises with large legacy estates. It is not a modeling, documentation, or semantic layer tool, so if those are your gaps, this isn't the one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Purpose-built migration automation combining AI code translation with data-parity validation&lt;/li&gt;
&lt;li&gt;Fixed-price, outcome-based engagements with guaranteed timelines reduce project risk&lt;/li&gt;
&lt;li&gt;Cross-database Data Diff gives value-level proof that migrated data matches the source&lt;/li&gt;
&lt;li&gt;Also useful after migration for CI/CD data diffing on dbt pull requests&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Focused on migration and testing, so no modeling, documentation, or semantic layer coverage&lt;/li&gt;
&lt;li&gt;Migration pricing is quote-based and not published&lt;/li&gt;
&lt;li&gt;Value concentrates in large or one-off migration projects, which may not justify the cost for smaller teams&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Custom, quote-based. Migration projects are scoped at a fixed price based on model count and complexity. Platform pricing for Data Diff and CI is also available on request.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Ellie.ai
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1ygeai7e9sevu8ich27m.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1ygeai7e9sevu8ich27m.png" alt="Ellie.ai" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Ellie.ai is a semantic data modeling platform built for collaborative data product design. It supports full-stack modeling, conceptual through logical to physical, so business and technical stakeholders can work on one canvas. Features include AI-assisted modeling, a business glossary, notes and annotations, and export to PDF, image, or DDL.&lt;/p&gt;

&lt;p&gt;Ellie integrates with 170+ business data solutions and source systems through an open API, including Snowflake, Microsoft Fabric, Purview, Collibra, and dbt. It also works with Data Vault tools such as WhereScape and VaultSpeed. That positions it as a direct alternative to SqlDBM for teams that want to design and document models before generating dbt or warehouse code.&lt;/p&gt;

&lt;p&gt;It's aimed at mid-size to large enterprises, especially financial services, that need business-friendly modeling and alignment between data architects, analysts, and domain experts. The honest limitation is that it's more design-time than runtime. It doesn't execute transformations or serve metrics the way dbt does, and users have noted that complex business processes can be hard to model.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Business-friendly, collaborative modeling across conceptual, logical, and physical layers&lt;/li&gt;
&lt;li&gt;Built-in business glossary and AI-assisted modeling support documentation and shared understanding&lt;/li&gt;
&lt;li&gt;Open API and 170+ integrations, including dbt, Snowflake, Fabric, and Collibra&lt;/li&gt;
&lt;li&gt;Transparent entry-level pricing with a Solo plan&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Design-time tool only, with no transformation execution or metric serving&lt;/li&gt;
&lt;li&gt;Smaller customer base than established modeling vendors (G2 cites 50+ customers)&lt;/li&gt;
&lt;li&gt;Users report that complex business processes can be hard to model&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; The Solo plan is listed at €49 per month for a single user license. The Enterprise plan adds team collaboration, hierarchical folders with security, and advanced AI, and is priced by contacting sales. A free trial is available.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Atlan
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj8csoo38ibuimd8992ty.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj8csoo38ibuimd8992ty.png" alt="Atlan" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Atlan is a collaborative data catalog and governance workspace that many modern-stack teams run alongside dbt. It ingests dbt metadata and parses column-level lineage from dbt models. It also adds impact analysis on GitHub pull requests and AI-assisted documentation.&lt;/p&gt;

&lt;p&gt;Atlan is really targeting the gaps in dbt's native catalog, which doesn't cover lineage across the wider stack: ingestion tools, BI dashboards, other warehouses. It's built for adoption by analysts and business users as well as engineers, with discovery, glossary, data quality signals, access policies, and governance workflows.&lt;/p&gt;

&lt;p&gt;It is not a modeling, transformation, or migration tool, and it doesn't replace the dbt Semantic Layer. What it does is make documentation and metric context discoverable and trustworthy across the organization. It suits mid-size to enterprise teams with multiple tools in the stack that need governance beyond what dbt provides on its own.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Strong column-level lineage parsed from dbt and extended across the stack&lt;/li&gt;
&lt;li&gt;User experience accessible to non-engineers, which helps documentation actually get used&lt;/li&gt;
&lt;li&gt;Pull-request impact analysis and AI-assisted documentation speed up upkeep&lt;/li&gt;
&lt;li&gt;Broad connector coverage and fairly transparent packaging for the category&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A catalog and governance layer, not a modeling, transformation, or migration tool&lt;/li&gt;
&lt;li&gt;Production use typically needs a paid plan, since the free tier is outgrown quickly&lt;/li&gt;
&lt;li&gt;Enterprise-oriented pricing can be steep for small teams&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; A free tier exists but is limited. Paid tiers are quote-based and depend on seats, connected sources, and governance features. Vendr data shows annual contracts commonly ranging from about $15K to $150K+, with a median near $50K per year.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Cube
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faiilhik06h9i68ip63v0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faiilhik06h9i68ip63v0.png" alt="Cube" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Cube is a universal semantic layer platform. You define metrics and data models once, then deliver them through SQL, REST, and GraphQL APIs to BI tools, embedded analytics, and AI agents. The open-source Cube Core is self-hostable. Cube Cloud is the managed version, with a semantic IDE, workbooks and dashboards, and caching and pre-aggregations to speed up queries.&lt;/p&gt;

&lt;p&gt;Unlike dbt's Semantic Layer, which is tied to one dbt project, Cube serves metrics to any downstream tool. Its dbt integration reads a dbt project directly on Premium plans and above, and plenty of teams run both side by side.&lt;/p&gt;

&lt;p&gt;Cube suits data teams that need governed metrics across several BI tools, or customer-facing analytics. The honest tradeoffs: it is a semantic layer, not a documentation or migration tool, and metric definitions live in Cube's own format that other tools can't read. The dbt integration is also gated behind higher-priced plans.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Tool-agnostic semantic layer that serves any BI tool, app, or AI agent&lt;/li&gt;
&lt;li&gt;Free open-source core and a free cloud tier&lt;/li&gt;
&lt;li&gt;Pre-aggregation and caching improve query performance beyond what the warehouse alone provides&lt;/li&gt;
&lt;li&gt;Can run alongside dbt, with dbt project integration on Premium and above&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Metric definitions live in a Cube-specific format that other tools cannot read&lt;/li&gt;
&lt;li&gt;dbt integration is gated to higher-priced plans&lt;/li&gt;
&lt;li&gt;Covers the semantic layer only, with no documentation depth or migration automation&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; A free plan includes semantic modeling, workbooks, and analytics chat. The Starter plan is listed at about $40 per user per month on some review sites. Premium and Enterprise plans are consumption-based, per Cube Compute Unit, with annual minimum commitments, such as around $10K per year for Premium on one listing. Published rates vary between sources, so confirm with Cube directly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Verdict
&lt;/h2&gt;

&lt;p&gt;Most of these tools are good at one thing. Datafold is excellent for migration. Atlan is excellent for cataloging. Cube is excellent as a universal semantic layer. Ellie.ai is strong on conceptual modeling. dbt is the backbone of everything.&lt;/p&gt;

&lt;p&gt;But if you want visual modeling, documentation, a governed semantic layer, and migration support all in one place that actually integrates with dbt in a production-grade way, SqlDBM is the pick. It generates dbt YAML, pushes to Git, imports your manifest for unified lineage, and layers a semantic model on top of a governed physical foundation. That combination doesn't really exist anywhere else, and the enterprise track record (John Holland, Mercadona, Les Mills, Pfizer, DocuSign) backs it up.&lt;/p&gt;

&lt;p&gt;Pair it with dbt and you've covered the full stack: visual design, documentation, semantic definitions, and migration, with transformation and metric execution handled by dbt itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does SqlDBM replace dbt?&lt;/strong&gt;&lt;br&gt;
No. SqlDBM complements dbt. It handles visual modeling, documentation, semantic definitions, and generates dbt YAML that dbt then executes. The two work together.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's the difference between SqlDBM's semantic layer and dbt's Semantic Layer?&lt;/strong&gt;&lt;br&gt;
dbt's Semantic Layer defines metrics in code within a single dbt project. SqlDBM defines governed semantic views visually on top of warehouse schemas, propagating schema changes automatically and serving one trusted definition to BI tools, dbt, and AI systems across projects.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which tool should I pick for a one-off legacy migration into dbt?&lt;/strong&gt;&lt;br&gt;
Datafold if you want a vendor-run, fixed-price migration with data-parity validation. SqlDBM if you want to own the migration internally with visual gold-layer modeling and dbt YAML generation, which is the pattern teams like John Holland used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need a catalog like Atlan if I use SqlDBM?&lt;/strong&gt;&lt;br&gt;
It depends on scope. SqlDBM handles modeling-centric documentation, lineage, and semantic definitions. Atlan is broader cross-stack cataloging (ingestion, BI, multiple warehouses). Large enterprises often run both.&lt;/p&gt;

</description>
      <category>data</category>
      <category>database</category>
      <category>documentation</category>
      <category>sql</category>
    </item>
    <item>
      <title>Best Data Warehouse Schema Documentation Tools (2026): SQLDBM, dbt, DataHub, Atlan &amp; SchemaSpy Compared</title>
      <dc:creator>Dainius Remeika</dc:creator>
      <pubDate>Thu, 08 Oct 2026 08:20:57 +0000</pubDate>
      <link>https://dev.to/danremake/best-data-warehouse-schema-documentation-tools-2026-sqldbm-dbt-datahub-atlan-schemaspy-1na3</link>
      <guid>https://dev.to/danremake/best-data-warehouse-schema-documentation-tools-2026-sqldbm-dbt-datahub-atlan-schemaspy-1na3</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1yv9nzfk69gf7of40jqe.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1yv9nzfk69gf7of40jqe.png" alt="header" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Schema documentation used to be the thing teams promised to do "next sprint" and then never did. In 2026, that excuse doesn't hold up. Warehouses are bigger, teams are more distributed, and AI systems are reading your metadata to decide what a column actually means. If your docs are stale or missing, everything downstream suffers.&lt;/p&gt;

&lt;p&gt;I spent a few weeks digging into the tools people actually use to document Snowflake, Databricks, BigQuery and similar warehouses. Some are modeling-first. Some are catalog-first. One is a free command-line generator that's been around forever. They all approach "documentation" from a different angle, and that difference matters more than most buyer guides admit.&lt;/p&gt;

&lt;p&gt;Here's my honest take on the five I'd actually consider: SqlDBM, dbt, DataHub, Atlan, and SchemaSpy. I'll explain what each one does well, where it falls short, and who it's really for.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Evaluated These Tools
&lt;/h2&gt;

&lt;p&gt;I looked at a few things that matter for real documentation work. How quickly a new team member can go from "connected to the warehouse" to "reading a useful description." Whether docs stay in sync with the actual schema or drift the moment someone runs a migration. Support for modern warehouses, especially Snowflake, Databricks, and BigQuery. Governance features like ownership, tags, and glossary. And collaboration, because documentation is a team sport and a one-person wiki always rots.&lt;/p&gt;

&lt;p&gt;I also weighed pricing honestly, including what you pay in engineering time for the free options.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. SqlDBM - Best Overall
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqqx9ban9f547wxsl7joc.png" alt="SqlDBM" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The schema documentation tool that doesn't just describe your warehouse, it governs the blueprint underneath it.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;After spending real time with every tool here, SqlDBM is the one I keep coming back to. It's cloud-native, browser-based, and code-free. Nothing to install, no local files to babysit, and it handles the full documentation lifecycle in a way the others don't quite match.&lt;/p&gt;

&lt;p&gt;What makes it stand out in this category is how tightly documentation is woven into the modeling workflow. You don't document &lt;em&gt;after&lt;/em&gt; the fact. You build the docs as you model, with descriptions, logical names, custom governance metadata fields, and full rich-text documentation pages living right next to the physical schema. The AI Copilot can generate descriptions and logical names across entire schemas in a single action, which is a huge time-saver when you're staring down hundreds of tables. Mercadona, Spain's largest supermarket chain, governs nearly 5,000 tables in SqlDBM and even uses the SqlDBM API to auto-generate dbt models deployed to BigQuery. That tells you something about how well it scales.&lt;/p&gt;

&lt;p&gt;For warehouse coverage, SqlDBM was the first online tool to support Snowflake back in 2019, is a Databricks Validated Data Partner, and a Google Cloud Partner. Reverse engineering, forward engineering, and documentation are purpose-built for the warehouses most teams actually run. Over 300 Snowflake clients use it today. Les Mills governs 1,000+ Snowflake tables with it as their all-in-one development, discovery, governance, and CI/CD tool after they rejected erwin on usability grounds.&lt;/p&gt;

&lt;p&gt;The thing that genuinely separates SqlDBM from the rest of this list is its semantic modeling layer. You can define semantic views that layer business context directly onto physical schemas, giving BI tools, dbt models, and AI systems one governed definition of what your data actually means. Standalone semantic tools like dbt or Cube skip visual modeling. Visual modeling tools like erwin or Hackolade skip the semantic layer. SqlDBM bridges both in one workspace.&lt;/p&gt;

&lt;p&gt;With 400,000+ users, a 4.7-star G2 rating, and back-to-back Database Modeling Solution of the Year wins at the 2023 and 2024 Data Breakthrough Awards, it's the most proven option in this roundup. PwC reported a 25 percent reduction in modeling time, which translates directly to faster, more complete documentation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Built-in schema documentation with custom governance fields, rich-text pages, and an AI Copilot that auto-generates descriptions across entire schemas. Docs happen as you model, not after.&lt;/li&gt;
&lt;li&gt;Purpose-built for modern warehouses. First online tool to support Snowflake (300+ Snowflake clients), Databricks Validated Data Partner, and Google Cloud Partner, with native reverse and forward engineering.&lt;/li&gt;
&lt;li&gt;Unique semantic modeling layer bridges physical schema docs and business context in one workspace. No other visual modeling tool does both.&lt;/li&gt;
&lt;li&gt;Proven at scale: Mercadona governs nearly 5,000 tables, Les Mills manages 1,000+ Snowflake tables, and PwC reported a 25% reduction in modeling time.&lt;/li&gt;
&lt;li&gt;Real-time multi-user collaboration with column-level lineage, dependency analysis, and Git/CI/CD integration keeps docs accurate and version-controlled.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Advanced governance and semantic features have a learning curve. New users may need a few sessions to fully leverage them.&lt;/li&gt;
&lt;li&gt;Supports all major cloud warehouses but doesn't extend to every niche or legacy database engine.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; SqlDBM is quote-based and scales with team size. Enterprise packaging covers premium support, SSO, and advanced security options. There's a free tier so you can start modeling and exploring documentation features before committing. Contact sales for a tailored quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. dbt (dbt Core / dbt Cloud)
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3axgw44nzikrj1unj5h2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3axgw44nzikrj1unj5h2.png" alt="dbt (dbt Core / dbt Cloud)" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;dbt is an open-source transformation framework for analytics engineers. Teams write SQL models, and dbt compiles, runs, and tests them in the warehouse. For documentation, descriptions live in YAML next to the code. Running &lt;code&gt;dbt docs generate&lt;/code&gt; and &lt;code&gt;dbt docs serve&lt;/code&gt; produces a searchable site with model and column descriptions, tests, and a lineage DAG at the model level.&lt;/p&gt;

&lt;p&gt;Because the docs come from the same repo as the transformations, they get versioned in Git and reviewed in pull requests. That's great for engineering discipline. dbt Cloud, the managed platform, adds a hosted IDE, scheduling, a semantic layer, and a catalog-style Explorer for browsing project metadata.&lt;/p&gt;

&lt;p&gt;dbt is a good fit for SQL-fluent teams that already build their warehouse layer in dbt. It documents what dbt builds. It isn't a visual modeling or ER design tool, and it won't document tables created outside dbt unless you add sources manually. Most teams end up pairing it with a modeling tool or a catalog.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Docs live in version-controlled YAML next to transformation code, reviewed and deployed with the models.&lt;/li&gt;
&lt;li&gt;Auto-generated lineage graph and docs site with no extra tooling.&lt;/li&gt;
&lt;li&gt;dbt Core is free and open source, with a large community.&lt;/li&gt;
&lt;li&gt;Descriptions and tests feed downstream catalogs like DataHub and Atlan.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Only documents what dbt builds. No visual ER modeling or forward engineering from a design.&lt;/li&gt;
&lt;li&gt;The static docs site can be slow on large projects, with limited governance features.&lt;/li&gt;
&lt;li&gt;Writing and maintaining YAML descriptions is manual work.&lt;/li&gt;
&lt;li&gt;dbt Cloud costs rise with seats and model builds.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; dbt Core is free. dbt Cloud has a free Developer plan for one seat. Third-party guides list the Starter plan at about $100 per developer seat per month, with up to 5 seats, 1 project, and 15,000 successful model builds per month. Overage runs about $0.01 per extra model. Enterprise is custom, reported at roughly $200 to $400 per seat per month. Confirm current prices on the dbt Labs pricing page.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. DataHub
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flzou8qqp73he23l6plf0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Flzou8qqp73he23l6plf0.png" alt="DataHub" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;DataHub started at LinkedIn and is now maintained by Acryl Data, which sells the commercial DataHub Cloud. DataHub Core is open source under Apache 2.0. It ingests metadata from warehouses, BI tools, orchestrators, and dbt, then gives teams a central place to search datasets, read schema and column descriptions, assign owners, apply tags and glossary terms, and trace lineage, including column-level lineage.&lt;/p&gt;

&lt;p&gt;The architecture is API-first and event-driven, which suits engineering-led teams that want to customize and extend things. DataHub Cloud is the managed version. It adds governance workflows, data quality and freshness monitors, and AI-assisted features.&lt;/p&gt;

&lt;p&gt;DataHub fits mid-size and large organizations with a platform engineering team, an open and heterogeneous stack, and the appetite to run infrastructure. It documents and governs existing assets. It isn't a tool for designing new schemas or generating DDL.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;DataHub Core is free under Apache 2.0, no license fee.&lt;/li&gt;
&lt;li&gt;Broad connector coverage and column-level lineage in the open-source edition.&lt;/li&gt;
&lt;li&gt;API-first, extensible, with an active community.&lt;/li&gt;
&lt;li&gt;Ingests dbt metadata, so it pairs well with dbt docs.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Self-hosting a multi-service stack takes real platform-engineering effort and ongoing maintenance.&lt;/li&gt;
&lt;li&gt;Key features like freshness and anomaly monitors are in the paid Cloud tier.&lt;/li&gt;
&lt;li&gt;DataHub Cloud has no public pricing page, and the AWS Marketplace list price is steep for small teams.&lt;/li&gt;
&lt;li&gt;It's a catalog, not a modeling tool. No visual schema design or forward engineering.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; DataHub Core is free (Apache 2.0), but you pay to host and operate it. DataHub Cloud is sold through sales. The AWS Marketplace listing shows the Discover &amp;amp; Govern package at roughly $75,000 for 12 months, covering up to 20 monthly active users (about $3,750 per user). Custom enterprise pricing is available.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Atlan
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj8csoo38ibuimd8992ty.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj8csoo38ibuimd8992ty.png" alt="Atlan" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Atlan is a commercial active metadata platform and catalog aimed at modern data teams. It connects to warehouses, BI tools, dbt, and orchestrators, and builds a searchable catalog with automated column-level lineage, business glossaries, data quality signals, and ownership. There's also an AI assistant for finding and describing assets.&lt;/p&gt;

&lt;p&gt;The interface is designed for both technical and business users. It supports collaboration features like embedding context in Slack and Jira, and it has policy and governance controls plus APIs for automation. Reviewers often praise the UI and lineage views. The common complaints are a learning curve on advanced features and fairly high list prices that usually come down through negotiation.&lt;/p&gt;

&lt;p&gt;Atlan is a good fit for mid-size to enterprise organizations that want a polished managed catalog and want business users participating in documentation. Like other catalogs, it documents and governs existing assets. It doesn't replace a schema design or modeling tool.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Modern, intuitive interface that works for engineers and business users.&lt;/li&gt;
&lt;li&gt;Automated lineage and broad integrations with warehouses, BI, and dbt.&lt;/li&gt;
&lt;li&gt;AI-assisted discovery and documentation, plus collaboration and governance workflows.&lt;/li&gt;
&lt;li&gt;Managed SaaS, so no infrastructure to run.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pricing isn't published, and reviewers describe list prices as steep for smaller orgs.&lt;/li&gt;
&lt;li&gt;Learning curve on more advanced features.&lt;/li&gt;
&lt;li&gt;It's a catalog and governance layer, not a tool for designing schemas or generating DDL.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Custom, quote-based, with no public price list. Pricing is typically based on licenses and connectors. Real affordability depends on negotiated discounts at scale. Contact Atlan for a quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. SchemaSpy
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvel9az2300q7knnntmur.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvel9az2300q7knnntmur.png" alt="SchemaSpy" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SchemaSpy is a long-running open-source database metadata analyzer. It connects to a relational database over JDBC, reads tables, columns, keys, indexes, and constraints, and produces a static HTML report. The report has clickable table pages, hyperlinked foreign keys, embedded ER diagrams, and reports on anomalies like tables without primary keys or indexes. Graphviz draws the diagrams.&lt;/p&gt;

&lt;p&gt;It supports many JDBC-compatible databases, can infer relationships where foreign keys are missing, and runs from the command line or a Docker image. That makes it easy to drop into CI so documentation regenerates after each migration.&lt;/p&gt;

&lt;p&gt;SchemaSpy fits developers, DBAs, and small teams that want free, on-demand schema docs they can hand to non-technical stakeholders. It's a read-only generator. No collaborative editing, no governance workflow, no cross-tool lineage, no model design. The output reflects what's physically in the database at the moment you ran it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pros:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Completely free and open source.&lt;/li&gt;
&lt;li&gt;Generates a navigable HTML site with ER diagrams in a single run.&lt;/li&gt;
&lt;li&gt;Anomaly reports flag missing keys and indexes, and relationships can be inferred.&lt;/li&gt;
&lt;li&gt;Easy to automate in CI/CD or Docker so docs stay in sync.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Cons:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Requires Java and Graphviz, and setup can be fiddly.&lt;/li&gt;
&lt;li&gt;Static, read-only output with no collaboration, glossary, or governance.&lt;/li&gt;
&lt;li&gt;No cross-system or column-level lineage, and large schemas produce crowded diagrams.&lt;/li&gt;
&lt;li&gt;Dated UI, no design or forward-engineering capability.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Pricing:&lt;/strong&gt; Free and open source, no paid tiers. Your only costs are the infrastructure and time to run it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Final Verdict
&lt;/h2&gt;

&lt;p&gt;If you're documenting a modern cloud warehouse and you want one tool that handles design, documentation, governance, and a semantic layer in the same workspace, SqlDBM is the clear pick. The AI Copilot alone makes a dent in the "we have 2,000 undocumented tables" problem, and the semantic modeling layer is something none of the other tools here offer in combination with visual modeling.&lt;/p&gt;

&lt;p&gt;That said, the right choice depends on what your team already does. dbt is a great fit if your warehouse layer is already dbt-driven and you're happy maintaining YAML. DataHub makes sense if you have a platform team that wants an open, extensible catalog. Atlan is the polished SaaS catalog for enterprise teams with budget. And SchemaSpy is a solid, no-cost way to get HTML docs out of any JDBC database when that's all you need.&lt;/p&gt;

&lt;p&gt;For most teams building on Snowflake, Databricks, or BigQuery in 2026, though, SqlDBM is the one I'd start with.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is schema documentation really different from a data catalog?&lt;/strong&gt;&lt;br&gt;
Yes. Catalogs like DataHub and Atlan document and govern assets that already exist. Modeling tools like SqlDBM document the schema as part of designing and evolving it, so docs stay in sync with the blueprint instead of trailing behind it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I use dbt and SqlDBM together?&lt;/strong&gt;&lt;br&gt;
Absolutely. Many teams design and document the physical schema in SqlDBM, then build transformations in dbt. Mercadona even uses the SqlDBM API to auto-generate dbt models.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What's the cheapest way to get decent schema docs?&lt;/strong&gt;&lt;br&gt;
SchemaSpy if you're comfortable with Java and Graphviz, or dbt Core if your warehouse layer is already in dbt. Both are free. Just budget the engineering time to set them up and keep them running.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why does the semantic layer matter for documentation?&lt;/strong&gt;&lt;br&gt;
Because docs that only describe physical columns don't tell BI tools or AI systems what a column &lt;em&gt;means&lt;/em&gt; for the business. A semantic layer gives you one governed definition that everything else can trust, which makes documentation genuinely useful instead of just technically complete.&lt;/p&gt;

</description>
      <category>database</category>
      <category>dataengineering</category>
      <category>documentation</category>
      <category>tools</category>
    </item>
  </channel>
</rss>
