| Prev | Advanced Operations Guide | Next |
Special Notes on the Configuration Utility
This section contains information to help you understand the Configuration utility, which is described in the following sections:
- Ensuring Configuration Changes Take Effect
- Connecting to Different Machines
- Interpreting Parameter Settings
When you start the Configuration utility, it is ready to configure client requesters and the engine on the local machine if one is present.
Ensuring Configuration Changes Take Effect
Most engine Configuration parameters require the database engine to be reloaded after they have been changed. You can re-load the engine in one of two ways:
- reboot the server machine
- stop and re-start the engine as described in Chapter 2 of Pervasive.SQL User's Guide.
In addition, changing client parameters often requires the client to be restarted. To re-load the client, simply exit all applications that depend on Pervasive.SQL and restart them.
Connecting to Different Machines
The Configuration utility can configure both local and remote engines as well as local client components; however, each engine must be configured separately. To configure a particular Pervasive.SQL engine:
- Open the Pervasive Control Center and double-click Pervasive.SQL Engines.
If you wish to configure a machine that is not in your engines list, it must first added:
- Expand the desired engine and expand the Configuration section beneath that engine.
If you are not logged into the server, you are prompted to enter your user name and password at this time. You must have full local administrator-level rights on the machine where the database engine is running, or be a member of the Pervasive_Admin group on the machine where the database engine is running, to view or change the engine configuration options.
- Expand all available options beneath Configuration. The options available will vary depending on the platform of the engine you are trying to configure.
When you are connected to a remote machine, you can view and change only engine components. Client components (such as on workgroup and workstation engines and client machines) can only be configured locally on each machine.
Note
If you have engines registered that are not running, you may encounter delays in PCC as it periodically attempts to contact these engines. To eliminate the delay, unregister the "dead" engines. You can minimize the delay by performing the following procedure:
In PCC, right-click Pervasive.SQL Engines and choose Properties. Set Poll interval (seconds) to 999. Click OK. You can also disable polling completely by clearing Enable service state polling on the same panel.
Interpreting Parameter Settings
Under each option, there are a number of parameters, which are displayed in the following table:
If you cannot find information about a particular Configuration setting, click on the Find Setting icon on the tool bar. Enter the name of the desired setting and a list of case matches is displayed. You can display the setting information by clicking on the desired setting.
The following table outlines the functionality of the Configuration utility:
For each parameter appearing in Configuration, you can double-click the parameter to see a window showing the minimum, maximum, default, and current value of the parameter.
Access to Client Configuration Settings
All operating system users have permissions to modify the client configuration parameters.
| Prev Configuration Utility Overview |
Contents Up Check for Revisions | Next Configuration Utility Tips |