The client configuration options are available in all the different installation setups. These options must be configured separately for each workstation, which includes servers acting as workstations. You can configure the client using the graphical utility Pervasive PSQL Control Center or the command-line interface utility bcfg. For PCC, see Using Pervasive PSQL Control Center in Pervasive
PSQL User's Guide. For bcfg, see Configuration Through CLI Utility.
The following table is a mapping of all the available client configuration options and their settings.
Table 13 Client Configuration Settings
Configuration Option Parameter Name
Access Gateway Durability
Number of Load Retries Use IDS
Use Local MicroKernel Engine Use Remote MicroKernel Engine Wire Encryption
Wire Encryption Level Cache Engine Allocate Resources at Startup
Windows Client Configuration Parameters
Access
Access contains the following configuration settings: Gateway Durability Number of Load Retries Use IDS
Use Local MicroKernel Engine Use Remote MicroKernel Engine Gateway Durability
Communication Protocols Enable Auto Reconnect Supported Protocols Connection Timeout Performance Tuning Use Cache Engine
Security Runtime Server Support
Application Characteristics Embedded Spaces Verify Key Length Splash Screen Table 13 Client Configuration Settings
Configuration Option Parameter Name
Type Range Default Units Requires Engine Restart
Number of Load Retries
This setting specifies the number of times the MicroKernel Router attempts to connect to the target engine.
Use IDS
This setting is primarily for use with legacy applications that used Pervasive PSQL (IDS). IDS functionality is now integrated into the core product and IDS is no longer available as separately installed components. The integration of IDS requires that you reconfigure your client/server environment.
Typically, an application provides its own file location information. As an alternative, IDS provided file location mapping based on information in a text file, idshosts.
If your applications do not use the mapping feature through idshosts, set Use IDS to Off to improve performance.
If your applications already use idshosts, or if you prefer to use this alternative method to map file locations, set Use IDS to On. See
Using the idshosts File.
Type Range Default Units Requires Engine Restart
Numeric 0 to 65536 5 None Not applicable
Type Range Default Units Requires Engine Restart
Boolean On Off
Windows Client Configuration Parameters
Use Local MicroKernel Engine
This setting determines whether a local application tries to connect to a local engine. If set to Off, no attempt is made to connect to a local engine.
Use Remote MicroKernel Engine
This setting specifies whether the MicroKernel Router allows access to a Server or Workgroup engine running on a remote server. If this value is set to On, and Use Local MicroKernel Engine is set to On, the remote server is tried first.
Wire Encryption See Wire Encryption.
Note Client-side wire encryption settings are not used by the Pervasive JDBC and ADO.NET access methods. For them, encryption can be specified using the connection string. See
Type Range Default Units Requires Engine Restart
Boolean On Off
On None Not applicable
Type Range Default Units Requires Engine Restart
Note Client-side wire encryption settings are not used by the Pervasive JDBC and ADO.NET access methods. For them, encryption can be specified using the connection string. See
Connection String Overview in JDBC Driver Guide and Defining Basic Connection Strings in Data Provider for .NET Guide.
Cache Engine
These settings apply only when the cache engine is running. TheWorkgroup engine doubles as a cache engine. Note, however, that the cache engine is not used if a database server engine is running. Cache Engine contains the following configuration settings: Allocate Resources at Startup
Back to Minimal State if Inactive Cache Allocation Size
Max MicroKernel Memory Usage Minimal State Delay
Allocate Resources at Startup
This setting instructs the cache engine to allocate resources, including threads and memory buffers, when the cache engine is started.
If you turn this option off, the cache engine does not allocate any
Type Range Default Units Requires Database Engine Restart
Boolean On Off
Windows Client Configuration Parameters
Back to Minimal State if Inactive
This setting displays only if the Workgroup engine is running.
This setting causes the cache engine to free considerable memory and thread resources to the system and return to a minimal state after a certain amount of time without any active clients. The time interval is specified by the value of Minimal State Delay. The cache engine reallocates resources when another client becomes active.
Cache Allocation Size
This setting specifies the size of the Level 1 cache that the MicroKernel allocates; the MicroKernel uses this cache when accessing any data files.
Type Range Default Units Requires Database Engine Restart
Boolean On Off
Off None Not applicable
Type Range Default Units Requires Database Engine Restart Numeric 1 megabyte to the amount limited by memory (see Note below) Initialized dynamically at first start-up megabytes (see Note below) Not applicable
remove memory from the system, you must modify this setting manually to take best advantage of the new amount of memory available.
Note If you use Pervasive PSQL Clients prior to Pervasive PSQL v10, the value for cache allocation size must be specified in bytes, with a minimum of 64 KB (65,536 bytes). The maximum is limited by the amount of memory.
Max MicroKernel Memory Usage
This setting specifies the maximum proportion of total physical memory that the cache engine is allowed to consume. L1, L2, and all miscellaneous memory usage by the cache engine are included. The database engine uses less if the specified proportion is not needed or not available.
If the value zero (0) is specified, then dynamic caching is turned off. In this case, the only cache available is L1, the size of which is specified by Cache Allocation Size.
For more information on tuning performance, please see Tuning Performance.
Minimal State Delay
This setting displays only if the Workgroup engine is running.
Type Range Default Units Requires Database Engine Restart
Windows Client Configuration Parameters