Recommended Configuration Settings for Pervasive.SQL V8

Article ID: 869860
Expand all | Collapse all

TechKnowledge Content

The information in this document applies to:

- Great Plains Standard on Pervasive.SQL

Issue

What are the recommended configuration settings for Pervasive.SQL V8?

Resolution

The settings below pertain only to Pervasive.SQL V8. Refer to the following TechKnowledge documents for all other versions of Pervasive.

Knowledge Base Article - Recommended Configuration Settings for Pervasive.SQL 2000 (SP1, SP2A)
Knowledge Base Article - Recommended Configuration Settings for Pervasive.SQL 2000i (SP3, SP4)

Pervasive.SQL V8 configuration settings can be viewed and changed from the Control Center.

NT/2000 Server

1. Go to Start | Programs | Pervasive.SQL V8 | Control Center.
2. Click the Plus sign next to Pervasive.SQL Engines.
3. Click the Plus sign next to the Server name.
4. Click the Plus sign next to Configuration.
5. Click the Plus sign next to Server.

NetWare Server

1. At a client workstation, go to Start | Programs | Pervasive.SQL V8 | Control Center.
2. Right-click on Pervasive.SQL Engines.
3. Choose Register New Engine.
4. Enter the name of the NetWare Server and choose OK.
5. Click the Plus sign next to NetWare Server name.
6. Click the Plus sign next to Configuration.
7. Enter a username and password for a user with Administrative/Supervisory privileges.
8. Click the Plus sign next to Server.

Recommended Server Settings for Pervasive.SQL V8

Single-User/Multi-User
Communication Buffer Size
Communication Buffer Size - 20% of Physical Memory up to 32 mg*
MKDE Communication Buffer Size - 20% of Physical Memory up to 32 mg*

Communications Protocols
Supported Protocols - Specific One**

Memory Usage
Allocate Resources at Startup - ON
Back to Minimal State if Inactive - OFF

Performance Tuning
Number of Input/Output Threads - 32

*Cache Allocation defaults to 20% of Physical Memory. It is recommended to leave the default setting for Cache Allocation, however, if you need to allocate memory elsewhere the Cache Allocation setting can be decreased to a minimum of 16777216. NetWare 5.1 and above servers defaults this setting to 1 MB. If you have a NetWare 5.1 or above server, verify the Cache Allocation setting is set to 20% of the Physical Memory or at least the minimum of 16777216.

**It is recommended to only specify the ONE protocol that is being utilized on the network. For an NT/2000 server, choose either the Microsoft TCP/IP or Microsoft SPXII. For a Netware server, choose either the Netware TCP/IP or Netware SPXII.

Once these settings have been changed, go to Edit | Apply to save the changes. The Pervasive services must then be stopped and started for the changes to take effect.

Windows NT - The engine can be restarted in 2 ways:

1. Go to the Control Panel | Services and find the Pervasive.SQL 2000 Transactional
and Relational Services. Both services must be stopped and then restarted in any order.

2. Open the Pervasive.SQL 2000i Control Center, right-click on the Server name
and choose Tasks | Restart Pervasive Services.

Windows 2000 - The engine can be restarted 2 ways:

1. Go to Start | Programs | Administrative Tools | Services and find the Pervasive.SQL
2000 Transactional and Relational Services. Both services must be stopped and then
restarted in any order.

2. Open the Pervasive.SQL 2000i Control Center, right-click on the Servername and
choose Tasks | Restart Pervasive Services.

Novell/Netware - The engine can restarted one way:

1. Go to the server console or through an Rconsole session and type in MGRSTOP and
then BSTOP. The MGRSTOP command may take some time to unload.

2. To restart the services, all that is necessary is the MGRSTART command.

Single-User Workstation - The engine can be restarted one way:

1. Right-click on the Pervasive Preload Icon in the System Tray and choose Stop
Engines and Exit.

2. Go to Start | Programs | Pervasive.SQL V8 | Engines | Pervasive.SQL Workstation
Engine to start the engine. The icon should now appear again in the System Tray.

Recommended Client Settings for Pervasive.SQL V8

Single-User
Access

Use Local MicroKernel Engine - ON
Use Remote MicroKernel Engine - OFF

Communication Protocols
Supported Protocols - NO CHANGE

Multi-User
Access
Use Local MicroKernel Engine - OFF
Use Remote MicroKernel Engine - ON

Communication Protocols
Supported Protocols - Select One*

*It is recommended to only specify the ONE protocol that is being utilized on the network. For Windows clients, choose either the Microsoft TCP/IP or Microsoft SPXII.

Once these settings have been changed, go to Edit | Apply to save the changes and close the Pervasive Control Center. The Pervasive services DO NOT have to be re-started for the client settings to take effect.

Additional Notes

1. The Client Cache Engine is a new feature with Pervasive.SQL V8. This setting is under Client | Performance Tuning | Use Cache Engine in the Pervasive Control Center and is defaulted to be ON. The Client Cache stores recently-used data file pages in local memory on the client workstation to allow improved performance with Read operations. It is recommended to leave the Client Cache Engine setting ON for all client workstations.

2. If you are experiencing sporadic network disconnections, you can enable the Pervasive Auto-Reconnect feature. To enable the Auto-Reconnect feature, complete the following steps:

Server

A. In the Pervasive Control Center, click on the Plus sign next to Pervasive.SQL Engines.
B. Click on the Plus sign next to the Server name.
C. Click on the Plus sign next to Configuration.
D. Click on the Plus sign next to Server.
E. Click on Communication Protocols.
F. Double-click on Enable Auto-Reconnect.
G. Choose ON and choose OK.
H. Choose Edit | Apply and re-start the Pervasive.SQL V8 Engines.

Client

A. In the Pervasive Control Center, click on the Plus sign next to Pervasive.SQL Engines.
B. Click on the Plus sign next to the Workstation name.
C. Click on the Plus sign next to Configuration.
D. Click on the Plus sign next to Client.
E. Click on Communication Protocols.
F. Double-click on Enable Auto-Reconnect.
G. Choose ON and choose OK.
H. Choose Edit | Apply to save the Client settings.

3. The TCP/IP Multi-homed setting must be enabled if there are multiple Network Cards at the server. This will allow the Microkernel engine to listen for client connections on all network cards. This is found under the Server | Communication Protocols | TCP/IP Multi-homed in the Pervasive Control Center and by default is set to ON for Pervasive.SQL V8.

4. The Transaction Durability setting is now by default set to OFF for Pervasive.SQL V8. This setting defaulted to ON for releases prior to Pervasive.SQL V8, therefore, it was recommended to set it to OFF for those releases.

This article was TechKnowledge Document ID: 29185

Properties

Article ID: 869860 - Last Review: October 15, 2011 - Revision: 3.0
Keywords: 
kbmbsmigrate kbretire KB869860
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com