Common Questions After Upgrading to Pervasive PSQL
This section contains information that you should read after running the installation program. If you are having problems with your installation, go to Chapter
16
,
Troubleshooting After Installation
, or get help online from the Knowledge Base at the Pervasive Software Web site.
How to Handle Data Source Names (DSNs)
The following table describes the procedures for upgrading your DSNs after you have installed the Pervasive PSQL upgrade.
Table 2
DSN Considerations After a Pervasive PSQL Upgrade
Scenario
Discussion
You have existing DSNs created with a version of Pervasive PSQL
prior to
Pervasive.SQL 2000
i
SP4
You must delete all existing DSNs before you upgrade. Once you have upgraded, re-create 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
SQL Engine Reference
.
You have existing DSNs created with Pervasive.SQL 2000
i
SP4 or a later version of Pervasive 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 “Pervasive 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
SQL Engine Reference
.
You do not have any Pervasive PSQL DSNs defined
For details about creating DSNs, see
DSNs and ODBC Administrator
in
SQL Engine Reference
.
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 “Pervasive ODBC Interface” to connect to a named database.
How Do I Convert My Files From Previous Pervasive Products?
Converting your data files to 9.x format is not required, but you must convert them if you wish to take advantage of new features offered by the Pervasive PSQL v11 SP3 engine.
Users of previous Btrieve versions: Use the Rebuild utility to convert your existing pre-6.0 or 6.x files to 7.x, 8.x, or 9.x format. For more information, refer to the
Advanced Operations Guide
.
What User License Was Installed with Pervasive 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
Pervasive PSQL User's Guide
for more information on the License Administrator utility.