AIToday
Large Language ModelsAI Business & IndustrySnowflake AI BlogPublished: Aug 23, 2026, 01:01 JST3 min read

Snowflake builds internal semantic layer to unify AI agents and dashboards

Snowflake builds internal semantic layer to unify AI agents and dashboards

Key takeaway

  • Snowflake built an internal semantic layer to give AI agents and dashboards one consistent definition of business metrics.

  • Without it, the same question yields different answers from different tables.

  • In July 2025, internal users ran over 320,000 queries through the semantic layer across sales, HR, and support teams.

3 Key Points

  1. What happened

    Snowflake built an internal semantic layer — a governed data abstraction that sits between raw tables and downstream consumers (dashboards, AI agents, user queries) — to standardize how the company's data is understood. In July 2025 alone, over 400 internal users ran more than 5,400 queries through the product data science agent using the semantic layer, and over 5,600 employees across all teams ran over 320,000 queries using the broader semantic layer.

  2. Why it matters

    Without a shared semantic layer, the same question (e.g., "What is an active customer?") yields different answers from different tables and metric definitions. AI agents compound this problem by processing new data sources faster than context can be curated. A semantic layer solves this by defining business logic once — metrics, dimensions, and relationships — so every interface (dashboard, Cortex Agent, ad hoc query tool) queries the same authoritative meaning, eliminating conflicting answers.

  3. What to watch

    Snowflake uses semantic view materializations to pre-aggregate metric and dimension combinations, cutting query latency and token usage for AI agents. The company also leverages Cortex Agents with custom routing instructions to scan semantic views and find the right data context automatically. Semantic views integrate with dbt for version control and CI/CD, and are interoperable with Apache Ossie (incubating), a vendor-neutral open standard.

Ask the AI about this article →

Context & Analysis

Snowflake's challenge mirrors a widespread enterprise problem: as data volume grows, the burden of context — understanding what each metric actually means — falls on data scientists who must manually reconcile conflicting definitions. The company found that raw data at petabyte scale becomes a liability rather than an asset when different teams define "active customer" or "compute spend" in incompatible ways. This friction multiplies when AI agents enter the picture. Because agents process new data sources at speed, information gaps widen faster than analysts can close them, creating a trust problem: when a Cortex Agent reports one number and a legacy dashboard shows another, no one knows which to believe.

Snowflake's solution — a semantic layer built with semantic views — treats data governance as a platform problem rather than a manual one. By defining metrics, dimensions, and relationships once in code (using YAML or SQL), the company ensures that every downstream consumer — whether a dashboard, a Cortex Agent, or an ad hoc natural-language query — reads the same authoritative definition. The semantic layer also automates two performance bottlenecks: materializations pre-aggregate metrics across dimension combinations so agents avoid expensive joins on raw event tables, and Cortex Agents use custom routing instructions to automatically scan and select the right semantic view for each query. The scale of internal adoption — over 320,000 queries across all teams in a single month — suggests the layer has crossed a threshold from specialist tool to foundational infrastructure.

FAQ

What problem does Snowflake's semantic layer solve?
Raw data alone creates conflicting answers. For example, the question "What is an active customer?" yields different results depending on which table and metric definition is used. A semantic layer defines business logic once — metrics like compute_spend and dimensions like region — so every interface (dashboard, AI agent, user query) queries the same authoritative meaning.
How does the semantic layer improve AI agent performance?
Agents querying raw data spend time finding and understanding multiple sources; with semantic views, they go directly to SQL execution. Agents are also more token-efficient because semantic views natively leverage pre-aggregated data and join relationships, reducing repeated computation.
What metrics did Snowflake see from using the semantic layer internally?
In July 2025, over 400 distinct internal users ran more than 5,400 queries through the product data science agent. Across all teams and agents using the broader semantic layer (in sales, HR, support, and other areas), over 5,600 employees ran over 320,000 queries in the same timeframe.
Snowflake AI BlogRead Original Article

Get the latest Large Language Models news every morning

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytime

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleTop AI labs hide containment plans for rogue models