Show: Delphi C++
Display Preferences

InterBase XE3

From RAD Studio XE3
Jump to: navigation, search

Go Up to Developing Database Applications

RAD Studio provides full support for InterBase XE3 databases. InterBase XE3 is installed with RAD Studio, in the following directory:

...\Embarcadero\RAD Studio\<n.n>\InterBaseXE3



If you want to use InterBase XE3 databases, you need to have:

  • The latest client version of InterBase
    (When you install RAD Studio, the correct client version of InterBase XE3 is automatically installed, unless you specifically deselect InterBase XE3.)
  • An x64 machine for the new platform support (if you want to use 64-bit)

The 64-bit edition can be installed only on the following operating systems:

  • Microsoft Windows Vista (64-bit)
  • Microsoft Windows 7 (64-bit)
  • Microsoft Windows 2008 R2 (64-bit)

RAD Studio XE3 support for InterBase

Integrated licensing for InterBase XE3

InterBase XE3 Developer Edition and InterBase XE3 ToGo are installed with RAD Studio XE3 (does not apply for Starter edition) and included in RAD Studio XE3 integrated license. This feature makes it easier for developers to create C++Builder and Delphi InterBase applications using RAD Studio.

ToGo Test Deployment license

The ToGo Test Deployment license allow users to test InterBase applications on deployment machines. For example, a user who is developing a Windows 32-bit InterBase application can use a ToGo Test Deployment license to test the application on other machines running 32-bit or 64-bit Windows, or Mac OS X. For more information, see Getting a ToGo Test Deployment license, or, The Complete InterBase ToGo Quick Start Guide.

InterBase ToGo dbExpress driver

RAD Studio contains the InterBase ToGo dbExpress driver, which enables easier interactions between InterBase ToGo databases and RAD Studio applications. The InterBase ToGo dbExpress driver makes it easier for developers to create InterBase ToGo applications with RAD Studio.

What's new in InterBase XE3?

For details, InterBase XE3 Readme is available here

ODBC Driver Improvements

The old DataDirect ODBC drivers have been replaced with a new offering of InterBase ODBC driver. However, the new InterBase ODBC driver might not be installed with InterBase XE3. The new ODBC driver is available for registered users to download at

Concurent Index Creation

With InterBase XE3, when restoring a database, the indexes for a table can be created all at the same time, after the table's data is restored. Also, re-computing index SELECTIVITY with SET STATISTICS can be concurrent. InterBase XE3 enables one assistant thread for such operations by default. You can adjust the number of concurrent threads available for such operations by modifying the configuration parameter MAX_ASSISTANTS in ibconfig file.

NO RESERVE SPACE for Database and User Tables

In InterBase XE3, a CREATE/ALTER TABLE clause is introduced to prevent space reservation and to maximize row packing. This clause is useful for tables whose rows are infrequently or never UPDATED or DELETED; whose queries are complex queries, such as aggregates and analytics that process a high percentage of rows; and where indexes are rebuilt and the database is frequently backed up and/or restored. Using this clause can lead to a 20% savings in storage space.

Physical Database Portability between Windows, MacOSX and Linux

With InterBase XE3, you can copy database files between Windows (32-bit and 64-bit), Mac OS X, and Linux. InterBase databases created on the development platform can be easily deployed to other supported platforms. You can create InterBase applications and InterBase databases on your development machine, and then easily deploy the applications and databases to other supported platforms, with some restrictions.

For more information on this feature, see the InterBase XE3 Readme file, which is installed with RAD Studio, typically at \RAD Studio\n.n\InterBaseXE3\Doc, and is also available online at

Features from previous releases

The following items represent a list of features from previous releases.

Stronger password protection

Stronger password protection is implemented in the new InterBase XE3 databases to comply with password requirements from the Payment Card Industry - Data Security Standard (PCI-DSS). This additional functionality supports a longer effective password length resulting in stronger protection.

The password can contain from 8 characters up to 32 characters.

Larger database cache settings for 64-bit InterBase

64-bit InterBase databases have now a larger cache. The limit for the 64-bit engine is 75 million pages, as compared to 750 thousand pages for 32-bit engines.

EXECUTE STATEMENT for Stored Procedures

Stored Procedure developers can embed three variations of EXECUTE STATEMENT within their Stored Procedures. The variations depend on the number of rows returned from the EXECUTE STATEMENT command. The three cases are:

  • No rows of data returned.
  • One row of data returned.
  • Variable number of rows returned.

Larger index key segment size

  • An index key can now be up to 4 bytes less than a quarter of the page size.
  • By default, InterBase databases are created with a 4Kb page size. This can be overridden up to a 16Kb page size by the database developer.
  • The 4Kb page size database would allow indexes that can accommodate 1020 bytes per key.
  • A 16Kb page size can accommodate 4092 bytes per key and so on.

ibconfig parameter: THREAD_STACK_SIZE_MB 2

The THREAD_STACK_SIZE_MB 2 ibconfig parameter controls the stack size of various threads in InterBase. The value is expressed as a multiple of megabytes per thread. The valid range is from 2Mb through 32Mb. If it is set beyond the range, the value defaults to 2Mb.

Table-specific blocking factor

The term blocking factor is used to denote the number of records stored in a block. InterBase employs a single database-wide blocking factor that maximizes the number of rows that can be stored on a data page.

Database fast sweep

Sweeping a database is a systematic way of removing outdated records. Periodic sweeping prevents a database from growing too large. In the past, sweeping slowed down system performance, and users disabled the automatic database sweep function because of the impact on product operations.

See Also

Personal tools
Previous Versions
In other languages