Supported Databases
DBModeler currently supports 14 database engines through its catalog-driven modeling and export system.
Current engine list
Section titled “Current engine list”| Engine | Notes |
|---|---|
| PostgreSQL | Strong native type support and sequence-aware workflows |
| MySQL | Table-engine-specific behavior and MySQL-style quoting |
| MariaDB | Similar operational model to MySQL with MariaDB-specific nuances |
| Oracle | Stricter foreign-key action behavior and Oracle-native type families |
| SQL Server | Bracket-style identifier quoting and SQL Server DDL behavior |
| SQLite | Lightweight engine support for compact schemas |
| IBM Db2 | Enterprise-oriented engine family support |
| Snowflake | Cloud data platform behavior and warehouse-oriented SQL patterns |
| BigQuery | Warehouse-style type handling and BigQuery-specific mappings |
| Redshift | AWS warehouse-oriented engine support |
| CockroachDB | PostgreSQL-adjacent engine family with its own caveats |
| YugabyteDB (YSQL) | PostgreSQL-family style support through the catalog |
| TiDB | MySQL-family style mapping with TiDB considerations |
| DuckDB | Analytical workflow support with DuckDB-specific mappings |
What support means in practice
Section titled “What support means in practice”Engine support in DBModeler does not mean identical SQL output across all databases.
It means the catalog provides engine-specific behavior for:
- data type mapping
- identifier quoting
- table storage options
- foreign-key action support
- ID generation strategies
- SQL command templates
Important caveat
Section titled “Important caveat”Some features vary by engine. Foreign-key actions, type fallbacks, sequence behavior, and enum handling are not identical across the supported set.
If you are working close to engine-specific limits, always review SQL preview before exporting.
Next: Data Type Mapping