The true open source database for Windows

Firebird (32-bit)

Firebird 2.5.0 (32-bit)

  -  6.45 MB  -  Open Source

Sometimes latest versions of the software can cause issues when installed on older devices or devices running an older version of the operating system.

Software makers usually fix these issues but it can take them some time. What you can do in the meantime is to download and install an older version of Firebird 2.5.0 (32-bit).


For those interested in downloading the most recent release of Firebird (32-bit) or reading our review, simply click here.


All old versions distributed on our website are completely virus-free and available for download at no cost.


We would love to hear from you

If you have any questions or ideas that you want to share with us - head over to our Contact page and let us know. We value your feedback!

  • Firebird 2.5.0 (32-bit) Screenshots

    The images below have been resized. Click on them to view the screenshots in full size.

    Firebird 2.5.0 (32-bit) Screenshot 1
  • Firebird 2.5.0 (32-bit) Screenshot 2
  • Firebird 2.5.0 (32-bit) Screenshot 3

What's new in this version:

Core Engine/API:
- The internal record compression routines exhibited some bugs
- A SELECT statement incurred more non-indexed reads in the third v.2.5 release candidate than the same statement in v.2.1.3
- ALTER DOMAIN was not possible in a database that had been migrated from an earlier version
- The WAIT mode and lock timeout parameters for the external transaction of EXECUTE STATEMENT were not matched to the corresponding parameters of the local transaction
- A regression introduced with the fix for CORE-2893 caused double processing of nodes when preparing a statement, prompting an abort to occur in the debug build
- Parameters would not work with NOT IN from a selectable stored procedure
- Incorrect LEFT JOIN result using table and derived constant subquery
- Attempt to run EXECUTE STATEMENT on an external data source failed when the data source was an InterBase 4.1 (ODS 8) database
- Batch inserts were noticeably slowed down if they were all executed in a single transaction and involved triggers that posted events

Server Crashes:
- The server would crash when isc_dql_exec_immed3_m() was called for CREATE DATABASE ... in a NULL transaction

Command-line Utilities:
- The gsec utility was sending its output list of users to stderr instead of stdout