Migration history & status
Every migration deploy is recorded in a per-project change-history table — schemachange's record of what's been applied, when, and with what checksum.
Two independent tables, not one
| Project | Table |
|---|---|
| Stock | VEHICLE_STOCK_DB.VEHICLE_STOCK_SCHEMA.SCHEMACHANGE_HISTORY |
| Redbook | SPECIFICATIONS_DB.REDBOOK_SCHEMA.SCHEMACHANGE_HISTORY |
There's no combined view across both. Checking whether a stock migration has run in prod says nothing about Redbook's state, and vice versa — check each project separately.
Checking status
cd src/stock/dbt # or src/redbook/dbt/migrations for Redbook
schemachange render -f migrations # Redbook: schemachange render -f .This is also what deploy-migrations.sh prints as its final hint after a successful deploy.
For a quick check without running the CLI, query the table directly through your admin Snow CLI connection:
snow sql -q "SELECT * FROM VEHICLE_STOCK_DB.VEHICLE_STOCK_SCHEMA.SCHEMACHANGE_HISTORY;" \
--connection snowflake-drive-staging-admin