Four dialects, written for each one
PostgreSQL, MySQL, BigQuery and SQL Server each get output written for that dialect — identifier quoting, type mapping and constraint syntax included — rather than a generic script with the names swapped.
- PostgreSQL
- MySQL
- BigQuery
- SQL Server (T-SQL)
Delta DDL for the change, not the whole schema
Delta DDL / Migration compares model versions and emits only what changed, so a review is about the alteration rather than a full re-read of the schema. Because versions are kept, the comparison is against a real prior state and not a remembered one.
Round trips both ways
DDL can also come in. Import an existing schema, model forward from it, and export again — the tool is a step in the pipeline, not a destination the model has to be re-typed into.
What this covers in the product
Every capability below is part of this area of Yantra Studio.
- Export ▸ DDL (SQL)
- Delta DDL / Migration
- Import DDL (SQL)
- Excel Data Dictionary
Questions
Which SQL dialects are supported?
PostgreSQL, MySQL, BigQuery and SQL Server, both for export and for reading an existing schema in.
Can it generate a migration rather than a full schema?
Yes. Delta DDL / Migration produces the difference between model versions.
Is there a data dictionary output?
Yes — an Excel data dictionary export covering entities, attributes, types and descriptions.
Related capabilities
-
The diagram and the data model are one artefact
Model entities, attributes and relationships once: the diagram and the data model are one artefact, with subject areas, a metadata repository and normal-form checks.
-
Know what a change breaks before you make it
Trace where data comes from and where it goes, map source to target, analyse the blast radius of a change, and compare environments.
-
One agreed meaning per term
Keep an agreed business glossary and a data dictionary attached to the model, and export the dictionary to Excel for people who will not open the tool.