 | Getting Started with Pervasive PSQL v9 SP2 (9.5) (Workgroup edition) (v9 SP2 (9.5) revision 1) |  |
|
Pervasive PSQL Clients have several settings that can be configured. This section informs you of the default values for three settings that are commonly used with clients. If you want to review all settings, and their default values, refer to the chapter Configuration Reference in Advanced Operations Guide. Steps for how to configure settings are in the chapter Changing Your Configuration, also in Advanced Operations Guide.
Default: Off
This setting determines whether the client and server attempt to reconnect to each other in the event of a network outage. If set to On, it allows the database connections to recover from intermittent or temporary network interruptions. If this value of this setting is Off, then the client returns a status code to the application immediately upon any failure to connect to the server, and the connection context is not preserved.
If you have this setting turned On, you can specify how long the client and database engine should attempt to reconnect by using the setting Auto Reconnect Timeout in the Server configuration.
Note
This setting is not available on 16-bit clients nor does the Pervasive PSQL Server for Linux support this setting. On Linux, you can use the Auto Reconnect feature only from a Linux client connecting to a Windows or NetWare server.
Default: varies depending on platform
TCP/IP is the default protocol for Pervasive PSQL. That is, TCP/IP is tried first if more than one protocol is set to be available.
This setting specifies the vendor protocols that the database engine should attempt to use. When more than one protocol is specified, upon start up, the engine attempts to connect on all specified protocols. The protocol that connects first is then used for the remainder of the session.
You can often improve initial connection performance by removing the protocols that are not used on your network. For example, if you have a Server engine on an all-TCP/IP network, removing SPX support may reduce the wait time during initial connections to the engine.
On Linux platforms, TCP/IP is the only supported protocol on the server.
Server engines do not support the NetBIOS protocol.
Default: 15 seconds
This setting specifies the number of seconds the requester should wait for a TCP/IP connect request to succeed before timing out.
|
Chapter contents
Prev topic: Configuring Network Communications for Clients
|