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

Snowflake builds internal AI layer to unify conflicting data definitions

Snowflake builds internal AI layer to unify conflicting data definitions

Key takeaway

  • Snowflake built a semantic layer to unify contradictory data definitions across its internal systems. One question like "active customer" previously returned different answers depending on the table queried.

  • The semantic layer, tested by over 5,600 employees across Snowflake running 320,000 queries in July 2025, ensures AI agents and dashboards all query consistent, governed data.

  • Text-to-SQL accuracy jumped from 20% to over 90% when semantic context was added.

3 Key Points

  1. What happened

    Snowflake built a semantic layer—a standardized data interface sitting between raw tables and users—to give both humans and AI agents consistent definitions across millions of internal data sources. In July 2025, over 400 internal users ran more than 5,400 queries through the product data science agent using this layer; across all teams and agents, more than 5,600 employees ran over 320,000 queries using the broader semantic layer.

  2. Why it matters

    Without shared context, the same question (e.g., "What is an active customer?") can yield different answers from different tables, forcing teams to rely on data scientists to clarify meaning. AI agents worsen this problem because new metrics and data sources are built faster than analysts can track. A semantic layer solves this by centralizing business logic once, then powering every dashboard, AI agent, and ad hoc query with the same governed definitions—eliminating conflicting answers.

  3. What to watch

    Snowflake's semantic views also improve AI agent performance directly: 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. Agents also run faster and use fewer tokens when querying through semantic views rather than raw data, reducing both latency and cost.

Ask the AI about this article →

Context & Analysis

Snowflake encountered a fundamental challenge: petabytes of internal telemetry became a liability rather than an asset because different tables defined the same business concept differently. A query about active customers, for example, could be answered three different ways depending on which table was consulted—using login recency, credit consumption, or account type. This fragmentation forced teams to rely on data scientists as interpreters, a bottleneck that became untenable when AI agents began querying at scale and speed, outpacing human review.

The company's solution—a semantic layer built on top of raw tables—acts as a translation boundary. Instead of exposing databases directly to dashboards or AI agents, semantic views sit in the middle, defining dimensions (like region), metrics (like compute spend), and their relationships once. Every downstream consumer—whether a dashboard, agent, or ad hoc query—then queries the same "golden layer." This centralization compounds benefits: queries run faster because they skip the discovery and sampling phase; agents consume fewer tokens because preaggregated data eliminates redundant computation; and accuracy improves because the model receives precise business context before it translates a natural-language question into SQL.

Snowflake's internal rollout also revealed an operational pattern: successful semantic layers require the same rigor as production software (version control, peer review, CI/CD), prioritize data engineering performance (ensuring underlying tables are fast and well-constructed), and curate relentlessly to prevent entropy. The company used popular dashboard tiles as a signal for which questions matter most, logged all queries to identify gaps, and routed new questions intelligently across semantic views using custom instructions and tools like Cortex Sense. This blend of governance, performance tuning, and user feedback appears critical to preventing the semantic layer itself from becoming a source of confusion.

FAQ

How much faster do AI agents run when using semantic views?
The article states agents querying raw data spend time finding, understanding and sampling multiple data sources, which can dominate runtime. With semantic views, agents go directly to SQL execution. Agents also become significantly more token-efficient when using table relationships and preaggregated data in semantic views, reducing repeated computation and lowering cost.
What was the accuracy improvement from adding a semantic layer?
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 Snowflake employees used the semantic layer in July 2025?
Over 400 internal users ran more than 5,400 queries through the product data science agent. Across all Snowflake teams and agents, more than 5,600 internal employees ran over 320,000 queries using 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 articleOneiric open source AI video generator released