Support for Windows Vista

In many aspects, Windows Vista is a departure from previous Windows operating systems. Among other features, Vista includes many changes to the Graphical User Interface (GUI), a new security model using User Account Controls (UAC), changes to the Windows firewall and additional Internet protection.

You may find that your software products-not just Pervasive PSQL products-behave differently under Vista because of the operating system itself.

Tips When Using Vista

Here are some tips for working with Windows Vista to help you use applications, including Pervasive PSQL applications.

Initially, client/server applications may not function correctly because of Vista's increased security. You may need to adjust some of Vista's security settings to enable client/server applications. See Security and File Permissions .

Windows Vista uses two main types of user accounts: standard users and administrators. The permissions differ for these two types of users.

If a standard user needs to perform a task that requires additional privileges, Vista prompts (run as administrator) for an administrator password.

Vista includes a built-in administrator, admin, whose account is disabled by default. The Vista installation requires that you create a secondary administrator account. You may also create additional administrator accounts after Vista is installed.

You can create system data source names (DSNs) only if logged on as an administrator. A standard user cannot create system DSNs.

Floating point precision has changed with Windows Vista. You may notice a change in the results from your application. Refer to the documentation for Windows Vista.

Pervasive PSQL and Vista

The Pervasive PSQL Server Engine, Workgroup Engine, and Client are Vista enabled for installation and execution. (See Operating System Support for a list of all supported platforms.)

This section discusses topics of which you should be aware when you install and use Pervasive PSQL on Windows Vista.

Types of Users

In addition to the Tips When Using Vista mentioned previously, the following behavioral differences with Pervasive PSQL occur depending on how you are logged on:

If you are logged on as a standard user, Vista prompts for an administrator password if you attempt to install Pervasive PSQL.

The Pervasive PSQL utilities create only system data source names (DSNs), not user DSNs. The creation of system DSNs requires that you are logged on as an administrator.

Internet Protocol

Pervasive PSQL supports Internet Protocol (IP) v4, not IP v6.

Tip
Consider changing the operating system default configuration from IP v6 to IP v4. Using IP v4 as the default prevents the delay caused by the database engine when the operating system network layer attempts to use IP v6 then must revert to IP v4. Refer to the operating system documentation for setting the IP default.

Configuration Settings

The registry configuration settings allow full access to all users. Pervasive PSQL configuration settings are persistent for all user types on Vista.

Security and File Permissions

Windows Vista enables the firewall by default. The Pervasive PSQL Server and Workgroup installation adds files to the firewall access list to enable access to the database engine. If the operating system security prompts you to unblock or allow communication with a Pervasive PSQL component, select OK (yes).

If you encounter problems with your client/server applications not working correctly after installation, check the firewall access list or the ports. You may need to adjust some of the security settings to enable client/server applications. You can add files to the access list or open ports. You do not need to do both.

If you want to add Pervasive PSQL components to the firewall access list, add the following:

For Pervasive PSQL 32-bit Server, ntdbsmgr.exe.

For Pervasive PSQL Workgroup, w3dbsmgr.exe.

For Pervasive PSQL 64-bit Server, ntdbsmgr.exe and ntdbsmgr64.exe.

If you want to opens ports, Pervasive PSQL communicates via the following ones: 3351 for the transactional interface, 1583 for the relational interface, and 139 for named pipes. Note that opening a port opens it for all access, not just for Pervasive PSQL.

Refer to the operating system documentation on security, firewall settings, and ports.

Workgroup Engine and Cache Engine

If a user starts the Workgroup Engine or Cache Engine in a Terminal Services session or in a multiple-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. That way, the engine is already running before the first user session starts.