Why convert FDB to SQL?
The main reasons are migration and backup: moving data to a different database system such as PostgreSQL, MySQL, or SQLite, or archiving schema and data in a portable, readable format. A SQL dump is engine-independent text that any DBA can inspect, modify, and replay.
How to convert FDB to SQL
DBeaver FREE
Connect to the .fdb in DBeaver, right-click the database or a table, and choose Tools > Dump Database or Export Data in SQL INSERT format to generate a .sql file.
IBExpert FREE
Register the .fdb in IBExpert and use Tools > Database Extract to script the schema DDL, then Tools > Data Pump to generate INSERT statements for the data.
About these formats
.FDB
Firebird Database
An FDB file is almost always a Firebird database - a single file that stores an entire SQL database (tables, indexes, stored procedures, and data). You connect to it using the Firebird…
Open .FDB details →
.SQL
SQL Script (Structured Query Language source / database dump)
A SQL file is a plain-text file containing SQL commands - schema definitions, INSERT statements, or queries. Open it in any text editor to read it; to use it, execute it against a database…
Open .SQL details →Quality & what to watch
- DBeaver generates ANSI SQL where possible, but Firebird-specific syntax such as BLOB subtypes, generators, and triggers may need adjusting before loading into a different database engine.
- IBExpert's Database Extract exports schema (DDL) but not data by default; use its Data Pump separately if you need both schema and INSERT statements.
- The Firebird engine must be installed before any client can read the
.fdb; an ODS version mismatch between engine and file will produce an error.
Frequently asked questions
Will the SQL dump work directly in MySQL or PostgreSQL?
Does DBeaver export both schema and data?
What credentials do I need to connect to the `.fdb`?
SYSDBA and password is masterkey, but these may have been changed by the database administrator.
