Concept card

Snowflake Cortex Analyst — NL-to-SQL

As of 2026-07-24T14:00:00Z

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Snowflake Cortex Analyst — NL-to-SQL?

Cortex Analyst trades setup effort for determinism — a formal YAML semantic model means every question mapping to the same measure always produces the same SQL, which is a compliance property in regulated reporting.

What it is

Cortex Analyst is Snowflake's native text-to-SQL capability, designed so that every natural-language question a business user asks maps to SQL through a formally authored semantic model rather than through free-form inference by the underlying language model. That single architectural choice — a declared semantic model instead of loose hints — is both Cortex Analyst's core strength and the main source of the effort required to deploy it well.

Why it matters: the semantic model is typically a YAML file, or a Snowflake-hosted semantic model object, that explicitly declares the tables involved, the dimensions available for filtering and grouping with their business-facing labels, the measures with their exact aggregation formulas, the join relationships between tables, and any fiscal-calendar or time-intelligence rules the business needs. When a user asks a question such as what revenue looked like by region in the second quarter, Cortex Analyst does not ask the model to invent an interpretation; it matches the question against the declared measure, dimension, and time definitions and generates SQL that implements exactly those mappings. Because the model is not guessing at metric formulas or join paths, two different phrasings of the same underlying question reliably produce the same SQL and the same answer.

Why it matters

Unlike Genie's free-text hints, Cortex Analyst forces the semantic-model author to declare exact aggregation formulas and join paths upfront.
That determinism matters most for regulated finance/compliance reporting, where the same question phrased differently must return the same answer every time.
The semantic model itself is the deployment bottleneck — accurately declaring every measure's formula for a replicated SAP GL dataset is the hard part.

Key points

Snowflake Cortex Analyst — NL-to-SQL is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.
Define owner, metric, threshold, support path, and rollback before scaling.
For non-AI use cases, still define quality, adoption, and operating ownership.
Leave a reusable operating asset: memo, checklist, control table, and exception log.
A premium answer is short, trade-off explicit, and defensible in a steering committee.

Terms used on this page

Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.
Adoption metric: The measurable behavior proving that the concept changed actual work after go-live.
Reusable IP: An artifact, checklist, or model that can be reused across clients without copying client-specific data.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →