Installation Review
This section provides you with a checklist to prepare you for installation and a set of commonly asked questions you should consider prior to installation. Please use this section as a review and a guide for a successful installation.
Quick Checklist
This checklist provides a review of the requirements needed in order to install Pervasive PSQL. Each of these items should be met prior to beginning the install process.
Your system hardware meets the minimum requirements to install Pervasive PSQL.
Your operating system and network environment is supported by Pervasive PSQL.
You have full administrator-level rights on the system where you plan to install Pervasive PSQL.
You understand the different options available in the Complete and Custom installation setup so you can install only the set of components you need.
You have reviewed the release notes in readme_psql.htm on the installation media for important, late-breaking warnings and information that could not be included as part of the user documentation but may be essential to your installation and use of the product.
If you are using a proxy server, you need to configure it to allow authorization of Pervasive PSQL. Configure the proxy server before you install Pervasive PSQL, or omit product authorization during installation and authorize the product after configuring the proxy server. See Authorization Access Through A Proxy Server in Pervasive PSQL User's Guide.
For Pervasive PSQL Vx Server, the machine, physical or virtual, on which you install the product must have Internet connectivity. (Internet connectivity is also required if the database engine is running.)
Your application vendor supports the Pervasive PSQL engine.
*Tip: If you are uncertain, contact your application vendor or review the documentation provided by your vendor to ensure that they support the Pervasive PSQL engine version and mode that you want to install.
Checklist for Windows Vista and Later Operating Systems
In addition to the items in the Quick Checklist, uses of Windows Vista and later operating systems should also have a clear understanding of User Access Control (UAC) on such operating systems, as well as understand the differences and limitations of Standard Users versus Administrators and have the appropriate permissions to install on the operating system.
Common Pre-Installation Questions
This section contains some of the most common questions asked prior to installing Pervasive PSQL. These questions represent special case scenarios that could possibly prevent a successful first-time installation. Before you begin installation, consider the situations represented by these questions, along with the Quick Checklist to determine if you have met all the requirements and if there are situations that need special attention.
Where do I install the Pervasive PSQL Server?
The Server engine must be installed on the same computer where the database files are located.
What about the Server’s client software?
The Pervasive PSQL Client is installed with every engine. So if you have a Pervasive PSQL engine installation, you can use your machine to connect to other remote engines as a client.
The Pervasive PSQL Client software must be installed on every computer that is expected to access the database.
Where do I install the Pervasive PSQL Workgroup?
Pervasive PSQL Workgroup can be installed on the same computer where the database files are located, or it can be installed on other computers to access the data over the network.
What about the Workgroup’s Client software?
The Pervasive PSQL Client (32-bit) is installed with every engine. If you access remote files through another Workgroup engine, the Client software is already installed, so you do not need to install the Client separately.
Where do I install Pervasive PSQL Vx Server?
Pervasive PSQL Vx Server can be installed on a physical machine or a virtual machine. In either case, the machine must have Internet connectivity. Internet connectivity is also required if the database engine is running.
How do I install Pervasive PSQL in a Microsoft Cluster Services environment?
If you plan to install Pervasive PSQL to a clustered environment using Microsoft Cluster Service (MSCS), you should first refer to High Availability Support in the Advanced Operations Guide. That chapter provides information about installing Pervasive PSQL in a clustering environment.
Running virtual machines (VMs) within an MSCS environment is typically quite involved. Consequently, running Pervasive PSQL Vx Server on VMs within an MSCS environment is more complicated than when not using VMs. Refer to the documentation from the various hypervisor vendors for running VMs within MSCS.
How do I install Pervasive PSQL in a Microsoft Terminal Services or XenApp environment?
If you plan to install Pervasive PSQL to a Microsoft Terminal Server or XenApp environment, you must be logged on to the console of the server as a user with system administrator rights to install. This can either be the physical console on the server or a remote console session.
*Caution: If you are installing the Workgroup or Client Engine on a Terminal Services Environment, the engine is installed by default to run as a service.
Only one instance of the database engine may run on any terminal server platform. You cannot run separate copies of the database engine within two or more terminal sessions. Refer to the Pervasive PSQL Web site for the list of Terminal Server Environments supported by Pervasive PSQL Server, Workgroup and Client (http://www.pervasivedb.com).
*Note: If a user starts the Workgroup Engine or Cache Engine in a Terminal Services session or in a multi-user environment where fast-user switching is used, other users on the system cannot access that engine nor can they start their own copy of the engine.

Status code 3032 results if a second user attempts to access another user's engine through the transactional interface.

If it is desirable to have multiple local users accessing a local engine, install the Workgroup or Cache Engine as a service.
How do I install my Pervasive PSQL database engine in a Microsoft Active Directory environment?
The installation of the Pervasive PSQL database engine in an Active Directory environment requires no special steps. Follow the installation steps as described in this manual for the product you have purchased.
You may install the Pervasive PSQL database engine on a domain controller if you choose. Be aware, however, that activity on the domain controller may affect the performance of the database engine. For this reason, you may prefer to install Pervasive PSQL on a server that is not a domain controller.
Where do I install my Pervasive PSQL Clients accessing Web applications?
For Web applications, the Client must be installed on the same computer as the Web server. Multiple Web server platforms require a client on each platform.
Does it matter if I use Pervasive PSQL Clients that are of a different version than that of the database engine?
Pervasive recommends that you use Clients that are the same version as the database engine. If you choose, you may use a Client that is an older version than the database engine with which it interacts. 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 Clients that are the same version as the database engine.
Clients that are a newer version than the database engine may or may not function correctly. Pervasive does not guarantee that newer versions of Clients will function correctly with older versions of the engine. Therefore, Pervasive recommends that you avoid the use of newer version Clients with an older engine.
Pervasive PSQL Vx Server
Because of the licensing differences with Pervasive PSQL Vx Server, Pervasive Software recommends that you use the Client that comes with Pervasive PSQL Vx Server. This helps ensure that your applications correctly count licenses and allows you to monitor license compliance from the Client.
Pervasive PSQL Vx Server can be used with Pervasive PSQL v10 Clients and Pervasive PSQL v11 Clients (see the following Note for Pervasive PSQL v11 Clients). However, the API’s available with such Clients may consume more sessions (over count). You may need to increase the number of licenses required for the same application usage. Also, the License Administrator with those Clients does not display all of the attributes of Vx Server licenses. License compliance can be accurately monitored only with the License Administrator installed with Pervasive PSQL Vx Server.
*Note: An update is available for Pervasive PSQL v11 Clients. If you apply the latest update, your applications correctly count licenses and you can correctly monitor license compliance with License Administrator from a Pervasive PSQL v11 Client. The update is available only for Pervasive PSQL v11, not products prior to Pervasive PSQL v11.
Does it matter where I download the Pervasive PSQL v11 SP3 install file?
Yes, it does matter. If you are installing a downloaded version of Pervasive PSQL, do not place the install file in a location that is listed in the PATH environment variables, as this can cause issues with file copying during install. Place the setup files in a location such as the Windows %temp% directory.
My system runs 24/7, is any time better than another for installing or upgrading to Pervasive PSQL v11 SP3?
The installation and upgrade should be performed during a period when all users are logged off the system and all data files are closed. As with any significant software installation, be sure to back up any important files on the target hard drive, including data files, before you begin the installation.
If you are performing an upgrade, keep the installation media and instructions from the old installation, in the unlikely event that you need to fall back to the previous version of the product.
How can I restrict users running in Terminal Services from changing Pervasive PSQL configuration settings, creating DSNs, and using the Monitor utility?
Pervasive PSQL clients running within Terminal Services client sessions can perform Pervasive PSQL administrative functions by default. For example, a user with such a client can change configuration settings for Pervasive PSQL, create DSNs, and use the Monitor utility. In prior releases, the ability to perform administrative functions was prohibited from the client.
To restrict this capability, a system administrator should follow these steps:
1
From PCC, open the properties for the MicroKernel Router under Local Client.
2
On the Properties dialog, check the option Restrict Administrative Functions from a WTS Client.
3
Click OK, then exit PCC and start it again for the setting to take effect.
Are there any special settings I need to make for my configuration that aren’t listed here?
Yes, there are some default settings in Pervasive PSQL that need to be adjusted if your configuration includes certain qualities. For example, the default settings need adjustment if you have:
•
Multiple network interfaces
•
Database Files that must not include Embedded Spaces
•
Microsoft Active Directory Service
•
A Network that is subject to outages
Please review Configuration for Special Installation Situations for these or other relevant issues, especially if you encounter problems after installation.
For Pervasive PSQL Vx Server, refer to Overview of Pervasive PSQL Vx Server in Pervasive PSQL Vx Server Product Guide for any configuration settings that might need adjusting.