AIToday
Large Language ModelsSnowflake AI BlogPublished: Aug 19, 2026, 06:01 JST

Snowflake builds semantic layer to unify AI agents and analytics

Snowflake builds semantic layer to unify AI agents and analytics

3 Key Points

  1. What happened

    Snowflake built an internal semantic layer—a standardized data context that sits between raw data tables and downstream consumers (dashboards, AI agents, etc.)—to resolve conflicting answers from inconsistent metric definitions across its business. In July 2025 alone, over 400 internal users ran more than 5,400 queries through the product data science agent using this semantic layer, and over 5,600 employees ran more than 320,000 queries across all Snowflake teams.

  2. Why it matters

    Without a shared semantic context, petabytes of raw data produce conflicting answers to simple questions (e.g., 'What is an active customer?' yields different results depending on which table and metric definition you consult). A semantic layer gives AI agents two concrete benefits: faster execution (agents skip time-consuming data discovery and sampling) and lower token costs (semantic views leverage pre-aggregated data, reducing repeated computation). In AtScale's benchmark testing, adding semantic context increased text-to-SQL accuracy from 20% to more than 90% across 40 business questions.

  3. What to watch

    Snowflake's semantic views integrate with dbt for version control and CI/CD, and support both YAML and SQL syntax. The views are also interoperable with Apache Ossie (incubating), a vendor-neutral open standard for semantic models. Performance relies on materialization—Snowflake can pre-aggregate specified metric and dimension combinations automatically to reduce query latency.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The core challenge Snowflake identified is that scale amplifies ambiguity: as organizations collect millions of data sources and petabytes of telemetry, the burden of clarifying what each metric means falls on data science teams. Human analysts must review queries to catch flaws and inconsistencies—a friction that becomes exponentially worse when AI agents are deployed, because agents can generate queries at scale without human oversight and may report conflicting numbers from different data sources. No one then knows which source to trust.

Snowflake's solution is to interpose a semantic layer between raw data and all downstream consumers (dashboards, AI agents, business intelligence tools). Rather than expose raw tables directly, the semantic layer translates governed business language into standardized logical names, metrics, and dimensions. This shift delivers three compounding returns: accuracy (AtScale benchmarks show text-to-SQL accuracy jumped from 20% to over 90% when semantic context was added), governance (access controls on semantic views enforce a single source of truth), and efficiency (AI agents become token-efficient and avoid repeated computation by querying pre-aggregated materializations instead of raw event tables).

Snowflake's internal results validate the model: in July 2025 alone, over 320,000 queries across all teams used the semantic layer, and the product data science agent served over 5,400 queries to 400 distinct users. The implementation treats the semantic layer with the same rigor as production software—full version control via dbt, CI/CD pipelines, peer review, and continuous evaluation against actual user questions logged in Snowflake. By making semantic views the default for both humans and AI, Snowflake has eliminated the need for each tool to maintain its own definitions and reduced the manual work of curating preaggregated data pipelines.

FAQ
What problem does the semantic layer solve?
Raw data often produces conflicting answers to the same question because different tables and metric definitions exist for the same concept (e.g., "active customer" varies by table). The semantic layer creates a single, governed definition—a 'golden layer'—so all tools and users query consistent meaning.
What performance improvements does the semantic layer deliver?
AI agents querying semantic views execute faster because they skip time-consuming data discovery and sampling. Agents also become more token-efficient by leveraging table relationships and pre-aggregated data in materializations, reducing repeated computation.
How does Snowflake materialize semantic views for performance?
Users declare which dimension and metric combinations need to be fast using the ALTER SEMANTIC VIEW command; Snowflake then pre-aggregates those slices in the background and intelligently maintains them, reducing response times.
Snowflake AI BlogRead Original Article

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleRobin Williams' children revive his Instagram to fight AI deepfakes