AIToday
Large Language ModelsAI Business & IndustrySnowflake AI BlogPublished: Aug 18, 2026, 22:00 JST3 min read

Snowflake builds internal semantic layer to unify data for AI agents

Snowflake builds internal semantic layer to unify data for AI agents

Key takeaway

  • Snowflake built an internal semantic layer—a standardized interface between raw data and AI agents—to eliminate conflicting answers when the same business question yields different results from different data sources.

  • In July 2025, the layer powered over 320,000 queries across internal teams, and benchmark testing showed semantic context increased text-to-SQL accuracy from 20% to more than 90%.

  • The company is now sharing best practices and integrating the semantic layer with the open standard Apache Ossie to let other platforms read its semantic models.

3 Key Points

  1. What happened

    Snowflake created an internal semantic layer—a standardized data interface that translates raw business data into consistent metrics and dimensions for both human analysts and AI agents. 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 across all teams ran over 320,000 queries through broader semantic layers in sales, HR, support and other areas.

  2. Why it matters

    Without a semantic layer, the same business question (like "What is an active customer?") yielded conflicting answers across different data tables and metric definitions. By curating one trusted semantic layer, Snowflake eliminated that ambiguity for both humans and AI. In benchmark testing cited in the article, adding semantic context increased text-to-SQL accuracy from 20% to more than 90% across 40 business questions on TPC-DS. AI agents also execute faster and consume fewer tokens when querying through semantic views rather than raw tables.

  3. What to watch

    Snowflake's semantic views now integrate with Apache Ossie (incubating), a vendor-neutral open standard, allowing semantic models to be read across platforms. The company is releasing best practices for versioning and testing semantic views using dbt integration and continuous integration/continuous delivery (CI/CD), and using Cortex Agents to intelligently route queries to the right semantic context.

Ask the AI about this article →

Context & Analysis

Snowflake's semantic layer addresses a foundational problem in enterprise data: when millions of data sources exist across a business, raw data alone does not answer questions reliably. The article illustrates this with the simple example of "active customer"—a single phrase that can mean three entirely different things depending on the table and metric definition used. This ambiguity compounds when AI agents are introduced, because agents operate at scale and speed, surfacing answers faster than humans can verify them. If one agent reports one number while a legacy dashboard shows another, no one knows which to trust.

The semantic layer solves this by sitting between raw data and downstream consumers (dashboards, AI agents, analytics tools) and translating business language into standardized metrics and dimensions. The article backs this with concrete results: in July 2025 alone, Snowflake's internal usage reached over 320,000 queries across teams, and benchmark data shows that semantic context raised text-to-SQL accuracy from 20% to more than 90%. Beyond accuracy, the semantic layer also improves performance and cost—agents spend less time discovering and sampling data, and consume fewer tokens when table relationships are pre-defined in the semantic view.

Snowflake's approach emphasizes treating the semantic layer with the rigor of production software: versioning it with dbt, testing it via the UI, and curating it relentlessly to match what users actually ask. The company is also moving toward interoperability by adopting Apache Ossie, an open standard, signaling that semantic layers may become a shared infrastructure layer across multiple platforms rather than a vendor-specific artifact.

FAQ

What problem does the semantic layer solve?
Without a shared semantic layer, the same business question yields different answers across different tables. For example, "What is an active customer?" could be defined as customers where days_since_last_login < 30, or where credits_consumed > 0 and account_type != 'TRIAL', or as a distinct count without region. The semantic layer creates one governed definition for all tools and users.
How much did query accuracy improve with semantic context?
In AtScale's benchmark testing, adding semantic context increased text-to-SQL accuracy from 20% to more than 90% across 40 business questions on TPC-DS.
How many internal queries used Snowflake's semantic layer in July 2025?
More than 5,600 internal employees across all Snowflake teams and agents ran over 320,000 queries using the broad semantic layer in sales, HR, support and other areas. Additionally, over 400 distinct internal users ran over 5,400 queries through the product data science agent and the semantic layer.
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 articleLLMs infer your age, wealth, gender from messages—and change responses accordingly

The AI news that matters, in one minute each morning.

Sign up free