Database Properties

You set properties for a database from a Properties dialog in PCC. The dialog contains a tree with the following property nodes:

Directories

Directories contains the following property settings:

Dictionary Location

This location specifies where the dictionary files (DDFs) reside on physical storage. This location must be on the same server to which you are connected (and where the database engine is running). The location must be formatted as though you are working directly at the server machine.

For example, if you are at a workstation connected to a Windows server where the database engine is running, and you want to create a new database on the C:\ drive of the server in the folder "mydata," you would enter the location as "c:\mydata." You would enter it this way even if you have a local network drive (for example, F:\) mapped to the server's C:\ drive.

Data Directories

Specify the location of the data file(s) in the Data File Locations field. Click on the Add File Location icon just above the directory list or click on the next available blank line in the list.

If you are specifying paths to data file(s) on this server, specify them in the same manner as for the dictionary locations. If you are entering paths to data files on another server, specify the full UNC path as shown below.

You can select a data file path in the list and click Remove if you decide not to include a specific data file location.

General

General contains the following property settings:

Bound Database

Indicates whether or not the database is bound. Binding a database prevents the DDFs or data files from being used in another database and prevents a data file from having two or more different table definitions within the same database.

For more information about bound databases, refer to Bound Database versus Integrity Enforced .

Integrity Enforced

Specifies whether integrity constraints (security, RI, and triggers) are enforced on the database. These constraints apply to Btrieve access to the data files as well as ODBC/SQL access.

See Setting Up Referential Integrity and Interactions Between Btrieve and Relational Constraints .

Encoding

The Pervasive JDBC driver supports character encoding. Encoding 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.SQL.

The encoding varies by operating system and language. By default, PCC sets the encoding to that 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 in Pervasive.SQL User's Guide.

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.SQL JDBC driver, see Using Character Encoding in JDBC Driver Guide, which is part of the Pervasive.SQL software developer kit (SDK). When using the Linux client, see Internationalization with the Client in Getting Started With Pervasive.SQL (Server Edition).

Relational Constraints

Relational Constraints displays a matrix that lists the relational constraints in effect for the database. See Interactions Between Btrieve and Relational Constraints .

Security

Security contains property settings (tabbed areas) for Database Security and Btrieve Security. See the chapter Pervasive.SQL Security for a complete discussion of security.