Before You Begin

Before upgrading to Pervasive PSQL v9 Service Pack 2, begin by reviewing the following documents for important information:

Chapter 2, Preparing to Install Pervasive PSQL - This chapter provides important information including system requirements and platform specific notes that are relevant to your operation.

README file - This file is located on the distribution media and contains late-breaking product news that could not be included in the product documentation.

Considerations

Once you have reviewed the latest product information, review this list of considerations to complete your upgrade installation preparation.

Pervasive PSQL Applications - Be aware of what applications you have currently using previous versions of Btrieve or Pervasive PSQL in your environment. Remember to include both client and server-based applications.

Vendor-Specific Information - Be sure and check with your application vendors for any specific information regarding their product with Pervasive PSQL.

TCP/IP Protocol - DOS applications require different requesters, preferably BTRBOX95, BTRDRVR, or BREQTCP.

Requesters or Server First? - Pervasive's upgrade and support policy dictates that you should always use requesters that are the same version as your Server database engine. Typically, a client requester that is an older version than the database engine with which it interacts will work. In some situations, depending on the type of SDK access method used by your application, an older version requester will not work with the database engine. Your application will be unable to communicate with the database engine. For those situations, you must use client requesters that are the same version as the database engine. See Engine and Client Version Conflicts .

Therefore, Pervasive recommends that you upgrade your requesters along with your server engine. You should install the server first and immediately upgrade all the client machines.

New Features and File Rebuilding - In order to make use of all the new version features, you must rebuild your data files so that they use the newest version file format. Advanced Operations Guide includes a chapter that details using the Rebuild Utility to rebuild your data files, if you would like to take advantage of newer features.

Back Up Data Files - Make sure you have a current backup of all your data files prior to beginning upgrade installation.

Platform Notes

This section contains installation information specific to the Windows platform.

To install Pervasive PSQL for Windows, you must have full administrator-level rights on the machine where you will install the product. You need administrative rights to make the client installation directories available to your workstations.

If you want your individual client machines to install the requesters from the server, you must copy the requester programs from the Pervasive PSQL installation media to folders on the server and give the clients permission to access those folders. Refer to the "Clients" folder on the installation media. You can also install clients directly from the installation media.

Migration of Existing Configuration Settings

During the installation process, all of your existing server configuration values are migrated to the new server engine, with several exceptions. The exceptions are documented in Table 7-1.

Table 7-1 Configuration Setting Values not Migrated
Configuration Setting	Value in V8
Server4Debugging4Trace File Location	C:\pvsw\bin\mkde.tra [default]; or bin\mkde.tra file in selected installation directory.
Server4Directories4 Transaction Log Directory	C:\pvsw\bin\mkde\log [default]; or bin\mkde\log subdirectory of selected installation directory.
Server4Compatibility4 Create File Version	9.x. By default, new data files are always created in the most recent file format.
Server4Memory Usage4 System Cache	Off. With the addition of Level 2 database cache in V8, the system cache should not be used.
Server4Data Integrity4 Transaction Durability	Off. With the addition of a new setting, Transaction Logging (default: On), Transaction Durability is not needed to ensure multi-file transaction atomicity and data integrity. If your application requires true Transaction Durability, you will need to use Configuration to turn this setting On.

Installing Over Existing Pervasive Products

If you are upgrading from older product versions such as Btrieve 6.15 and wish to make use of all the new version features, you must rebuild your data files so they use the latest file format. See Converting Data Files in Advanced Operations Guide section for detailed information on how to use the Rebuild Utilities to convert your data files.

If you install Pervasive PSQL v9 Service Pack 2 over an existing version such as Pervasive.SQL V8, Pervasive.SQL 2000, or Btrieve 6.15, then those products will be archived when you install Pervasive PSQL v9 Service Pack 2 so that there are no component conflicts. You can use Pervasive System Analyzer later to restore the archived products if necessary. Your licenses from previous Pervasive products are not migrated to Pervasive PSQL v9 Service Pack 2.

If you have any trouble with the following installation, see Chapter 19, Troubleshooting After Installation.

Accessing README file information

It is highly recommended that you go through the README file to find out the latest changes and additions to Pervasive PSQL v9 Service Pack 2. The README file is located in the root directory of the installation media.