Export SQL

Use SQL export to inspect the DDL DBModeler will generate for the current diagram or for a saved version.

What export includes

Depending on the context, DBModeler can generate:

The exact output depends on the selected database engine and whether you are exporting the current diagram or a version snapshot.

Open the SQL preview dialog before downloading or copying anything.

This lets you verify:

Previewing first is the fastest way to catch modeling or engine mismatches before the SQL leaves DBModeler.

For an initial schema, DBModeler typically generates a full DDL sequence.

That sequence can include:

pre-table custom scripts
sequences or other helper objects when required by the engine
CREATE TABLE statements
primary-key and foreign-key statements where the engine requires separate clauses
post-table custom scripts

For later versions, DBModeler generates migration-oriented SQL.

Instead of rebuilding the whole schema, the output is based on the diff between versions and can include ALTER TABLE statements for:

The catalog controls SQL generation details such as:

This means a field may export differently on PostgreSQL, MySQL, Oracle, or SQL Server even when the logical model is the same.

SQL export is focused on DDL. It does not try to generate application data migrations or arbitrary DML workflows for you.

If you need extra database logic around the generated DDL, use Custom SQL Scripts.