From the Excel model to SQL scripts, without redoing it by hand.
You define how your database should end up in a spreadsheet. Schema Forge compares it with your project’s scripts, detects the differences per table and generates the scripts to reach the target model.
- Target model in Excel
- Per-table gap analysis
- Generated SQL scripts
- ZIP download and history
Bringing the database to the new model is manual and error-prone.
Schema Forge automates the comparison and the writing of the scripts, and shows you what is missing in each table so you can review with judgment.
Model and reality out of sync
The model defined by the business does not match what is in the project’s scripts.
Differences hard to see
Comparing table by table by hand takes days and things get missed.
Scripts written one by one
Every column or table change is written and tested separately.
From a spreadsheet to ready scripts
-
1
You define the model
Each sheet in your Excel is a table and highlighted cells mark the target columns.
-
2
You pick your project
Schema Forge reads the SQL scripts your project already has, and can optionally use Explorer’s context.
-
3
The AI compares and generates
It analyzes the differences per table and generates the new scripts to reach the model.
-
4
You review and download
See the result, check the generation history and download everything in a ZIP.
Generating scripts does not execute a data migration. Review the SQL, prepare a backup and test in a validation environment before applying it.
Built to evolve databases
Model in Excel
Define the target model in a spreadsheet the business understands.
Per-table analysis
Differences between what exists and what should exist, table by table.
New SQL scripts
Generates the scripts to bring your project to the target model.
Generation history
Review, compare and delete previous generations of each project.
ZIP download
Take all the scripts of a generation in a single file.
With your project’s context
It can rely on Explorer’s criteria and on the entities detected in the code.
When to use it
Align the schema
Turn the target model defined in Excel into a concrete review of the project schema. Compare table-level gaps, review types and relationships with the team, and use SQL scripts as a starting point for controlled data evolution.
Prepare the destination
Prepare the target schema alongside application modernization. Gap analysis helps discuss which tables and columns should change, coordinating data work with the contracts the new backend will consume.
See what is missing
Use Gap Analysis, SQL Scripts and Summary to review output from different perspectives. Check conventions, constraints and compatibility with the chosen engine before adding scripts to your database change process.
Works with your files
Database changes under control
Review before applying
Scripts are generated for you to review; you decide when to run them.
Traceable history
Every generation is recorded per project.
Your data in your environment
The platform can run in your infrastructure.
Frequently asked questions
You may also like
Bring your database to the new model
Bring an Excel model and a project’s scripts: we will show you the differences and the generated scripts.