ODS (on-disk structure) is a number representing version of the database physical layout structure. When a new feature is added to the Firebird it might or might. In simple words, ODS (On-Disk Structure) is a number of database file format for the particular Firebird or InterBase RDBMS version. Almost all. Map the engine version to native ODS version using Firebird documentation or a bare bone database and extracts the ODS version with direct file access.
|Published (Last):||11 June 2007|
|PDF File Size:||18.75 Mb|
|ePub File Size:||8.11 Mb|
|Price:||Free* [*Free Regsitration Required]|
In the initial release, a database with an older ODS cannot be opened by Firebird 3. In order to work with a database with an older ODS it will be necessary to make a backup using gbak under the older server and restore it with gbak on Firebird 3.
The new ODS for these databases is The most popular platforms—Windows and Linux x64 bit —were not affected by the change. They were carefully checked to verify that, for them, there is no actual difference between ODS For non-Windows and non-Intel-Linux platforms, developers could not perform all the required checks.
The only figebird safe solution for them was the minor ODS upgrade.
Existing databases with ODS Under these conditions, there will be no problems opening existing databases with the new Firebird sub-release. Cross-platform copying of any ODS Our checks did not reveal any cross-platform compatibility firebrid between ODS The Implementation ID in the ODS of a database is deprecated in favour of a new field in database headers describing hardware details that need to match in order for the database to be assumed to have been created by a compatible implementation.
The three ID fields are just for information: The compatibility flags are checked for a match between the database and the engine opening it.
Currently we have only one flag, for endianness. As previously, Firebird firebirc not open a database on little-endian that was created on big-endian, nor vice versa. Maximum database size is increased to 2 32 pages previously 2 31 pages. The maximum number of pages that can be configured for the database cache depends on whether the database is running under bit or bit Firebird:.
Historically, transaction ID space was limited to 2 31 transactions, counted from the time the database was created. After that point, the database becomes unavailable until backup and restore is performed to reset the transaction ID counter back to zero.
Initially in Firebird 3. This makes the new limit roughly equal to 2.
All Firebird and InterBase On-Disk-Structure (ODS) versions – Firebird News
Later, it could be extended up to the 2 63 limit. The implemented solution has no additional storage overhead until the transaction counters grow beyond the 2 32 boundary.
Prior to Firebird 3. For Named Pipes a. For shared memory aka XNET protocol, it contained the local host name.
Starting with Firebird 3. It is likely to be abandoned in a future version. Per-table performance counters have been added to all of the monitoring tables. Operating system user name.
Protocol and osd library version. The PLAN is now included. Note A legacy provider for databases with ODS 8 to Implementation ID is Deprecated.
All Firebird and InterBase On-Disk-Structure (ODS) versions
Maximum Number of Page Buffers in Cache. Changes to System Tables. Changes to Client Address Reporting.
For information about authentication mapping, see Mapping of Users to Objects in the Security chapter.