Your warehouse vendor now sells the semantic layer too. Convenient.
Right up until half the business turns out to live in the other warehouse.
Both shipped something real
Snowflake Semantic Views and Databricks Metric Views are genuine improvements. Definitions live next to the data, governed by the platform's own model, queryable by that platform's AI features.
If your entire estate is on one platform, either will take you a long way.
Almost nobody's estate is on one platform
There's a warehouse, a lakehouse someone piloted, an operational Postgres, and a SaaS system that never got migrated. A warehouse-native semantic layer can only see its own warehouse.
| Consequence | What it looks like |
|---|---|
| Cross-platform joins | Fall back to hand-written SQL |
| Duplicate definitions | Same metric defined twice, drifting |
| Per-platform governance | Coverage is per-platform, so gaps are structural |
| Partial answers | Agent returns a confident number computed over two thirds of the data |
That last one is the dangerous failure. Nothing errors. The number is just wrong in a way nobody can see.
The walled garden problem
There is also an incentive question worth naming: a warehouse vendor's semantic layer is, among other things, a reason to move more data into that warehouse. That's not sinister — it's product strategy — but it means "should meaning live inside the warehouse?" is being answered by parties who benefit from one answer.
Meaning has to sit above the warehouse, not inside one of them: one versioned graph across the estate, join paths proven regardless of which engine holds the tables, compile-time policy applied uniformly, and dialect-perfect SQL emitted per target.
Adopt the native features. Just don't mistake them for the layer that spans your business.
The full breakdown — what each platform's feature does and where it stops, plus the cross-estate architecture — is here:
👉 Snowflake vs. Databricks: Why You Need an Autonomous Semantic Layer
Originally published at colrows.com/blogs/snowflake-databricks-semantic-layer
Top comments (0)