How to compare environments in Yantra Studio
Compare two environments and read the differences between them.
When this is useful
- Something works in test and fails in production, and the schemas are the suspect.
- A release is being prepared and you need to know what drift accumulated since the last one.
- An audit asks whether environments are actually aligned.
Before you start
- Access to the environments being compared.
Step 1: Open Env Compare
Env Compare sits in the Data menu.
Data ▸ Env Compare
Step 2: Read the differences
Work through the differences and separate the intended ones from the drift. Both look identical in a diff; only you know which is which.
Step 3: Produce the migration
Where the difference should be closed, Delta DDL generates the migration between what is modelled and what is deployed rather than a full create script.
Data ▸ Delta DDL / Migration
What happens next
Closing drift deliberately, with a recorded migration, is what stops the same comparison producing the same surprises next release.
Example
A staging environment compared against production revealed an index present in one and not the other — the entire explanation for a query that was fast in test and unusable live.
Tips
- Compare before a release, not during an incident. The information is the same; the pressure is not.
Limitations
- A comparison shows structural difference. Whether a difference matters is a judgement it cannot make for you.