Common Questions After Installing Pervasive.SQL

This section contains information that you should read after running the installation program. If you are having problems with your installation, go to Chapter 19, Troubleshooting After Installation, or get help online from our Knowledge Base website at http://support.pervasive.com/eSupport.

How to Handle Data Source Names (DSNs)

The following table describes the procedures for upgrading your DSNs after you have installed the Pervasive.SQL upgrade.

Table 7-2 How to Proceed After Installing Server and Client Software
If your situation is like this....	... then you should do this next:
You have existing Pervasive.SQL 7 DSNs already defined.	You must delete and re-create all existing Pervasive.SQL 7 DSNs before you can access existing databases. Follow the instructions provided in Pervasive.SQL User's Guide Chapter 2, sections Deleting DSNs and Setting Up Database Access on Windows.
You have existing Pervasive.SQL 2000 DSNs already defined.	You should be able to access your databases by connecting to the existing DSNs. Follow the instructions provided in Pervasive.SQL User's Guide, Chapter 2, section Accessing Data via ODBC From Other Applications.
You do not have any Pervasive.SQL DSNs defined	You should be able to connect to the sample DEMODATA database now. Refer to Pervasive.SQL User's Guide for general information on working with Pervasive.SQL. Refer to Advanced Operations Guide for detailed information on working with databases and database engines.

How Do I Convert My Data Files From Previous Pervasive Products?

You are not required to rebuild your data files from previous releases after you upgrade your version of Pervasive.SQL. Pervasive.SQL is completely backward compatible in respect to data file formats supporting file formats 6.x, 7.x, and 8.x.

However, note that certain Pervasive.SQL features and functionality are unavailable if you do not rebuild your data files to the latest version format.

The following table lists some of the main features of Pervasive.SQL releases to help you determine if you want to rebuild data files.


File Version	Product Features
6.x	Performance improvements Transaction Logging and Durability if your data file contains a unique key International Sort Rule (ISR) support
7.x	64 GB file size limit Transaction Logging and Durability if your data file does not contain a unique key
8.x	Turbo Write Accelerator
9.x	Higher than 64 GB file size (up to 128 GB) 8K page size

The Rebuild utility can convert older data files to the current Pervasive.SQL format. See Converting Data Files in Advanced Operations Guide.

How Do I Read the Online Documentation?

The documentation for Win32 platforms is in JavaHelp format. You access the documentation from the Pervasive program on the Start menu. Note that JavaHelp requires a Java Runtime Environment (JRE), which is installed by default with the Pervasive.SQL Server or Pervasive.SQL Client.

You can also view the documentation in the form of Adobe Acrobat (PDF) files. These PDF files are available on the Pervasive.SQL installation media in the "Books" directory.

A README file in the root directory of the distribution media lists important last-minute information.

How Do I Verify or Update My User License?

The License Administrator utility is documented in Pervasive.SQL User's Guide in the section License Administrator . Please see that document for information on user licenses.

Where Do Files Reside After Installing Pervasive.SQL 9 SP1 (9.1)?

Once installed, Pervasive.SQL files reside in the following directory structure.


\WINNT\SYSTEM32			Microsoft system files.
\Program Files\Common Files\Pervasive Software Shared
	\PSA		Pervasive System Analyzer
	\DOC		Online documentation
	\PVSWCORE		Pervasive Services
\PVSW
	\BIN		Pervasive.SQL engines, requesters and utilities.
	\CLIENTS		Pervasive.SQL client installation programs. (server only)
		\WIN	Pervasive.SQL Windows client installation program. Valid for Windows versions.
		\DOS	DOS Pervasive.SQL Requester files. These files must be manually copied to a DOS client.
	\DEMODATA		Contains sample database. (server only)
	\SAMPLES		Contains the sample database SAMPLE.BTR and UPPER.ALT, a sample Alternate Collating Sequence. (server only)