Jam SQL Studio DataGrip Version Control vs
Jam SQL Studio Database Blueprint
DataGrip pairs a general-purpose Git plugin with a DDL data source for keeping schema-as-files in your VCS. Jam SQL Studio's Database Blueprint is a dedicated schema-to-folder workflow with a built-in Git panel and a review-before-apply hand-off — and it versions table data alongside the schema. Here's how they compare.
Database Blueprint is in beta • Free for personal use • Mac, Windows, Linux
How Version Control Works in DataGrip
DataGrip inherits JetBrains' IDE version-control machinery, then layers a database-specific abstraction on top for schema. (JetBrains docs)
Bundled Git (and More) Plugin
DataGrip's Git functionality relies on the Git plugin, which is bundled and enabled by default. It also supports Subversion, Mercurial, and Perforce. You get a Version Control tool window, a Log tab showing commits across branches, and the usual commit / branch / push actions for your project folder.
DDL Data Source for Schema-as-Files
To version the database itself, DataGrip uses a DDL data source — a virtual view of the database structure built from SQL files that contain DDL statements. Storing those files in the VCS is how you keep the schema under version control.
Dump and Apply in Both Directions
You can dump changes from a real database into the DDL data source and share them through VCS, or pull changes and apply them back to a data source — synchronization in both directions runs through the DDL data source. JetBrains notes the Migration dialog that generates change scripts is still under development, and you may need to remove unnecessary DDL scripts manually.
DataGrip Version Control vs Database Blueprint
How DataGrip's Git plugin + DDL data source compares to Jam SQL Studio's Database Blueprint (beta).
| Capability | Jam SQL Studio — Database Blueprint | DataGrip — Git + DDL Data Source |
|---|---|---|
| Schema as one file per object | ✓ Table / view / proc / function / schema | DDL data source SQL files |
| Materialize whole DB to files | ✓ Refresh from DB | Dump to DDL data source |
| Built-in Git panel | ✓ Inside the tab | ✓ VCS tool window |
| Other VCS (SVN / Mercurial / Perforce) | ✗ Git-focused | ✓ Supported |
| Auto-generated commit messages | ✓ From changed object set | ✗ You write them |
| Drift preview (DB vs files) | ✓ Preview changes | Synchronize / diff data source |
| Three-way merge (local / baseline / live DB) | ✓ | ✗ |
| Apply folder back to DB with review | ✓ Reuses Schema Compare | Migration dialog (in development) |
| Version & sync table row data, not just schema | ✓ Captured row sidecars + row-level sync | ✗ DDL data source is schema only |
| Link one folder to Dev / Stage / Prod | ✓ Per-link MetaInfo | ✗ |
| Price | ✓ Free Personal tier | Free non-commercial; otherwise subscription |
| Runtime | ✓ Electron (fast startup) | JVM / IntelliJ platform |
What Database Blueprint Adds
A dedicated schema-version-control workflow instead of wiring up a DDL data source yourself.
One File Per Object
Refresh from DB writes a .sql file for every table, view, procedure, function, and schema — no manual data-source setup or globbing rules.
Git Panel In the Tab
Commit (auto-messaged), branch, pull, push, and resolve conflicts without leaving the Database Blueprint workspace.
Review Before Apply
Apply folder to DB reuses Schema Compare, so you see a full diff and the generated DDL before anything touches the target database.
Three-Way Merge
Separate clean merges from real conflicts across local edits, the last-refresh baseline, and the live database.
Table Data, Versioned Too
Opt a table into data capture and its rows land in a tracked Data/ folder. Sync data folder → DB pushes row-level inserts, updates, and deletes back to a linked database.
Full reference: Database Blueprint documentation.
Frequently Asked Questions
DataGrip version control vs Jam SQL Studio Database Blueprint.
Does DataGrip have version control?
Yes. DataGrip ships the JetBrains version-control integration: a bundled, enabled-by-default Git plugin (plus Subversion, Mercurial, and Perforce), with a Version Control tool window, Log tab, and commit / branch / push actions. To version the schema itself, DataGrip uses a DDL data source — a virtual data source built from SQL files of DDL that you store in the VCS and synchronize both ways with a real data source.
How does DataGrip put a database under version control?
Through the DDL data source. You keep its SQL files in Git, then either dump changes from a real database into it and commit, or pull changes and apply them back. JetBrains notes the Migration dialog that produces change scripts is still under development.
How is Database Blueprint different?
Database Blueprint is a dedicated workflow rather than a generic abstraction. It materializes the schema as one .sql file per object, keeps the folder in two-way sync with one or more linked databases, and ships a built-in Git panel plus an Apply folder to DB hand-off that reuses Schema Compare for review-before-apply. Database Blueprint is in beta.
Does Database Blueprint version table data too?
Yes — not just schema. During Refresh from DB you can opt any table into data capture, and Jam writes its rows to a tracked Data/ folder (a .data.sql upsert script plus a .data.json sidecar with the primary key and column types) that commits to Git alongside the DDL. Sync data folder → DB then diffs those rows against the live table and pushes row-level inserts, updates, and deletes to a linked database, with an Open in Data Compare hand-off for closer review. DataGrip's DDL data source versions schema, not table data.
Is Jam SQL Studio free like DataGrip?
Jam SQL Studio has a free Personal tier; DataGrip is free for non-commercial use and otherwise requires a JetBrains subscription. Database Blueprint is available in Personal mode for databases with up to 200 objects (tables + views + procedures + functions); larger databases require Pro. See the broader DataGrip alternative comparison.
Version-Control Your Schema with Database Blueprint
Download Jam SQL Studio free and keep your database schema in Git — no DDL-data-source setup required.
Comparing Database Source Control?
See how schema version control works in other SQL tools.
Learn more: Database Blueprint docs · Schema Compare