New: AZ Data now serves schema context to any MCP client — Claude Code, Cursor, and more. See how it works

Track

Real-time schema tracking

Every rename, drop, and type change in your Snowflake account — detected in minutes, not discovered in an incident.

1–5 minute polling

A scheduled hash-diff of INFORMATION_SCHEMA. Tight enough to matter, light enough that your warehouse won't notice.

No replication lag

ACCOUNT_USAGE can run 45 minutes to hours behind. We read INFORMATION_SCHEMA, which has none.

Least-privilege role

A read-only role scoped to metadata. No table data is ever read or leaves your account.

How detection works

Hash, compare, record.

Each poll fingerprints every table, view, and column. When a fingerprint changes, AZ Data records exactly what changed, when, and — where Snowflake exposes it — who ran the DDL.

  • Renames are tracked as renames, not as a drop plus a create
  • Type widenings and narrowings are flagged separately
  • Every change gets a stable ID you can reference in a PR or a ticket
Next: how changes get published

See a change land in under five minutes.

We'll alter a table in a demo account and watch the docs, the commit, and the agent context update live.

Talk to us