Database Engines

You can use PCC to work with database engines that are on your machine or with remote server engines. To work with a remote server engine, you must introduce it to PCC. This procedure is called registering the server.

Your local server is automatically registered to PCC when you install Pervasive PSQL v9 Service Pack 2. The local server appears in the Pervasive PSQL Explorer as the first entry under the Engines node.

To register a remote server engine

In Pervasive PSQL Explorer, right-click on the top node in the tree (Pervasive PSQL).

Click New 4 Server.

Identify the server that you want to register.

Type the name by which the server is identified on the network or type the IP address of the server.

Optionally, select the type of encoding.

The Pervasive JDBC driver supports character encoding, which allows you to interpret data through a specified code page so that it is formatted and sorted correctly. The code page interprets the string data stored in the database.

Note that PCC passes the encoding setting to the JDBC driver. The JDBC driver, in turn, uses the encoding setting to connect to the database. No conversion of the data already existing in the database takes place because of the encoding setting. The encoding setting in PCC has no effect on any other utilities or interfaces within Pervasive PSQL

The encoding varies by operating system and language. By default, PCC sets to the encoding used by the machine. For example, the encoding is 1252 for English on a Windows machine.

You can set encoding at the server level or at the database level. At the server level, the encoding applies to all new databases created on that server. See To register a remote server engine .

At the database level, the encoding applies only to that specific database and overrides the encoding setting for the server. You can change the encoding for the current database (the database for which you are logged in). For the encoding change to take effect, however, you must log out from the database then log in again.

For additional information on encoding when using the Pervasive PSQL JDBC driver, see Using Character Encoding in JDBC Driver Guide, which is part of the Pervasive PSQL software developer kit (SDK). When using the Linux client, see Internationalization with the Client in Getting Started With Pervasive PSQL (Server Edition).

Click Finish.

The server should now appear in the Pervasive PSQL Explorer window of PCC under the Engines node.

To log out from a database engine

These steps do not erase the data or database from the server. A logout only disconnects the communication between the database engine and the PCC on your computer.

In Pervasive PSQL Explorer, expand the Engines node in the tree (click the icon to the left of the node).

Right-click on the server engine from which you want to log out.

Click Logout (name).

Name reflects the name of the user currently logged in to the server through PCC. Name is anonymous if no specific user name and password were provided for a login.

Any nodes expanded for the database engine are collapsed.

To reconnect to a database engine

In Pervasive PSQL Explorer, expand the node in the tree for the server engine (click the icon to the left of the node).

To log in to a database engine

Right-click on the database name in the PCC Pervasive PSQL Explorer then click Logout (name).

Name reflects the name of the user currently logged in to the server through PCC. By default, name is anonymous, meaning that no specific user name and password were provided for a login.

Any nodes expanded for the database engine are collapsed.

Right-click on the database name.

Click Login.

Type a User Name and Password.

You can leave these blank to log in as "anonymous."

Click OK.

Database Engine Properties

See Configuration .