Upgrading to Pervasive PSQL v11 SP3 From a Previous Version
If you are upgrading a previous version of Pervasive PSQL to Pervasive PSQL v11 SP3, follow the same procedure as you would if you were installing for the first time. See Chapter 4, Installing Pervasive PSQL Server for Windows for detailed installation procedures.
If you are upgrading a version of Pervasive PSQL prior to Pervasive PSQL v10, Pervasive PSQL v11 SP3 archives the previous version before removing it.
If you are upgrading from much older versions such as Pervasive.SQL 2000i and wish to make use of all the new version features, you must rebuild your data files so they use the v9.5 file formats. See Converting Data Files in Advanced Operations Guide for detailed information on how to use the Rebuild Utilities to convert your data files.
An upgrade migrates configuration settings. For a version of Pervasive PSQL prior to Pervasive PSQL v10, only the configuration settings defined in ptksetup.ini are migrated.
Note that keys from previous Pervasive PSQL products are no longer valid if you upgrade to a new major release of Pervasive PSQL. (For example, an upgrade from Pervasive PSQL v10 to Pervasive PSQL v11.) You must have a key for the new major release to authorize Pervasive PSQL after upgrading.
Considerations When Upgrading to Pervasive PSQL v11 SP3
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. Don’t forget to include both client and server-based applications, such as ArcServe.
Vendor-Specific Information - Check with your application vendors for any specific information regarding their product with Pervasive PSQL.
TCP/IP Protocol - Make sure that your TCP/IP network is configured correctly (you should be able to PING the server by name), and that any firewalls between the clients and server (including firewalls on those computers) are configured to pass database traffic. See Windows FireWalls.
DOS Requester - DOS applications are only supported via the BTRBOX requester. Native DOS machines should be migrated to a Win32 platform before upgrading. DOS applications are not supported on 64-bit Windows platforms. Therefore, BTRBOX is not supported on 64-bit Windows platforms.
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.
Back Up Data Files - Make sure you have a current backup of all your data, database engine files and configuration prior to beginning upgrade installation