PreviousWhat's New in Pervasive PSQL v10 (v10) Next

Support for 64-bit Operating Systems and Applications

Chapter contents

Pervasive PSQL supports the transactional interface on native 64-bit operating systems running on machines with 64-bit architecture. The support applies only to the transactional interface and to the SDK interfaces Btrieve and DTI (see SDK Interfaces). The relational interface is 32-bit only. The relational interface functions the same on 64-bit operating systems as it has in previous 32-bit releases.

Database Products

Pervasive Software now offers 32-bit and 64-bit versions of the Server Engine and the client. The Workgroup Engine is available only in a 32-bit version. The following table summarizes the platforms on which the products can be installed and the type of applications supported by the product.

Table 1-1 Install Platforms and Application Support
Product
Install Platform
Local Applications1
Remote Applications1
32-bit
64-bit
32-bit
64-bit
32-bit
64-bit
Server Engine 32-bit

 

Server Engine 64-bit3
 

Workgroup Engine4

 

Client 32-bit

     
Client 64-bit
 

   
1 "Local" and "remote" are relative to the product. For example, a client can run an application that is local to the client itself but remote to the server engine.
2 The 32-bit Server installed on a Windows 64-bit machine runs under the Windows-on-Window (WOW) execution layer.
3 Only the transactional interface is 64-bit. The relational interface is 32-bit.
4 The Workgroup Engine is 32-bit only. A 64-bit version is not available.

Note that the 32-bit Pervasive PSQL products are supported on 64-bit operating systems. In addition, the 64-bit transactional engine and 64-bit DTI and Btrieve API are supported on 64-bit operating systems. Application created with a 32-bit interface can be used with the 64-bit Server engine.

SDK Interfaces

The 64-bit client supports 64-bit applications that use the Btrieve API or the distributed tuning interface (DTI). Other software development kit (SDK) interfaces are not supported for 64-bit access.

The header files for the Btrieve API and DTI have been enhanced to support 64-bit applications. For a 64-bit application using the Btrieve API, you need to define the preprocessor symbol BTI_WIN_64 (for Windows platforms) and link against w64btrv.lib.

For a 64-bit application using DTI, link against w6dba.lib.

Chunk Operations

Chunk descriptors are larger in size when used in a 64-bit application than when used in a 32-bit application. Pointers are 64 bit (8 bytes wide) in a 64-bit application.

Application
Chunk Offset (bytes)
Chunk Length (bytes)
User Data Pointer (bytes)
32-bit
4
4
4
64-bit
4
4
8

As with previous releases of Pervasive PSQL, the User Data field is only used in indirect chunk descriptors. You should initialize it to zero in direct chunk descriptors. Refer to the various chunk operations in the Btrieve API Operations chapter in Btrieve API Guide.

Registry

Registry changes apply more to the operating system and less to how your interact with Pervasive PSQL. However, because Pervasive PSQL now runs on 64-bit environments, some general information about the registry is useful background.

On 64-bit operating systems the registry is split at certain important nodes into a 32-bit section and a 64-bit section. Access to keys is redirected by default to the appropriate section depending on whether the calling application is 32-bit or 64-bit. The Windows API allows applications to request which specific section to access. Refer to your operating system documentation for specifics about registry architecture on 64-bit platforms.

The Pervasive PSQL components transparently access the 32-bit or 64-bit section of the registry as required.

Pervasive PSQL Settings

When Pervasive PSQL v10 is installed on a 64-bit Windows operating system, most components store their registry entries in the 64-bit section of the registry. In the 64-bit version of Pervasive PSQL, both 32-bit and 64-bit versions of certain components are present. Both versions read their settings from the same section of the registry. For example, if you enable debug tracing for the client components, the tracing applies to both 32-bit and 64-bit client components.

To read or modify commonly used settings, use Pervasive PSQL Control Center or the DTI API.


Chapter contents
Book contents

Prev topic: Support for Windows Vista
Next topic: Performance