Upgrading Your PSQL Installation for Windows
 
Upgrading Your PSQL Installation for Windows
Considerations for Upgrading
The following topics cover upgrading to the current release from a supported previous version. They include configuration settings migrated during the upgrade.
• Upgrading to PSQL v13 from a Previous Version
• Common Questions After Upgrading to PSQL
Throughout, PSQL without an explicit version number means all versions.
Upgrading to PSQL v13 from a Previous Version
If you are upgrading a previous version of PSQL to PSQL v13, follow the same procedure as you would if you were installing for the first time. See Installing PSQL Server and Vx Server for Windows for detailed installation procedures.
If you are upgrading a version of PSQL before PSQL v10, the installer 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 new features, you must rebuild your data files to either 9.5 or 13.0 file formats, depending on your needs. 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 PSQL before PSQL v10, only the configuration settings defined in ptksetup.ini are migrated. For PSQL v10 and later versions, an upgrade disregards any settings defined in ptksetup.ini and simply migrates all configuration settings.
Note that license keys from a previous release are no longer valid if you upgrade to a new major release, such as from v12 to v13. You must obtain a new key to authorize it.
Considerations When Upgrading to PSQL v13
Once you have reviewed the latest product information, review this list of considerations to complete your upgrade installation preparation:
*PSQL Applications – Be aware of what applications you have currently using previous versions of Btrieve or PSQL in your environment. Remember to include both client and server-based applications.
*PSQL Ecosystem Products – Existing installations of AuditMaster, Backup Agent, or DataExchange working with the version of PSQL to be upgraded must first be uninstalled. Before removing them, we recommend you capture their configuration settings to use in reinstalling and configuring their new versions after upgrading.
*Vendor-Specific Information – Check with your application vendors for any specific information regarding their product with PSQL.
*TCP/IP Protocol – Make sure that 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 supported only via the BTRBOX requester. Migrate native DOS machines to a Win32 platform before upgrading PSQL. BTRBOX and DOS applications are not supported on 64-bit Windows platforms.
*New Features and File Rebuilding – To make use of new features, you may need to rebuild data files to the newest format version. See the Rebuild utility in Advanced Operations Guide.
*Data File Backups – Before upgrading, make sure you have a current backup of your data, database engine files, and configuration settings.
Common Questions After Upgrading to PSQL
This section contains information that you should read after running the installation program. If you are having problems with your installation, see Troubleshooting After Installation or get help online from the knowledge base at the Actian website.
How to Handle Data Source Names (DSNs)
The following table describes the procedures for upgrading your DSNs after you have installed the PSQL upgrade.
Table 1 DSN Considerations After a PSQL Upgrade
Scenario
Discussion
You have existing DSNs created with a version of PSQL prior to Pervasive.SQL 2000i SP4
You must delete all existing DSNs before you upgrade. Once you have upgraded, recreate the DSNs to access the existing databases.
New DSNs should connect to a named database, not to an Engine DSN because Engine DSNs are deprecated.
See ODBC Connection Strings in ODBC Guide.
You have existing DSNs created with Pervasive.SQL 2000i SP4 or a later version of PSQL
You should be able to access your databases by connecting to the existing DSNs.
Note, however, the recommendation is that new or revised 32-bit applications should connect to a named database, not to an Engine DSN because Engine DSNs are deprecated.
If you want to port your 32-bit application to 64-bit, then make the following changes.
•If the application uses DSN-less connections that connect using “Pervasive ODBC Client Interface,” change the connection string to “PSQL ODBC Interface.”
•If the application uses Engine or Client DSNs, you must create 64-bit DSNs that connect to a named database. (Also note that on 64-bit Windows operating systems, 64-bit system DSNs are distinct from 32-bit system DSNs because of the registry design.)
See ODBC Connection Strings in ODBC Guide.
You do not have any PSQL DSNs defined
For details about creating DSNs, see DSN Setup and Connection Strings in ODBC Guide.
If you want to use DSN-less connections for 32-bit applications, use the connection string “Pervasive ODBC Client Interface” and connect to a named database. For 64-bit DSNs, use the connection string “PSQL ODBC Interface” to connect to a named database.
How Do I Convert Files from Previous PSQL Products?
Converting data files to 9.x format is not required, but you must convert them if you wish to take advantage of newer features offered by the PSQL v13 engine.
Users of previous Btrieve versions: You must use the Rebuild utility to convert existing pre-6.0 or 6.x files to 7.x, 8.x, or 9.x format. For more information, see Advanced Operations Guide.
What User License Was Installed with PSQL?
A trial license is installed if you leave the license number blank during installation.
There is no configuration necessary for the license. After installation, you can use the License Administrator utility to view your installed licenses. See the PSQL User's Guide for more information on the License Administrator utility.