Recommended Configuration Settings for Pervasive.SQL V8

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 otherversions of Pervasive.


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

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


NT/2000 Server


1.Go to Start| Programs| Pervasive.SQLV8|Control Center.

2. Clickthe Plus sign next to Pervasive.SQL Engines.

3. Clickthe Plus sign next to the Server name.

4. Clickthe Plus sign next to Configuration.

5. Clickthe Plus sign next to Server.


NetWare Server


1. At a client workstation, go to Start| Programs| Pervasive.SQL V8|Control Center.

2. Right-clickon Pervasive.SQLEngines.

3. Choose Register New Engine.

4. Enter the name of the NetWare Server and choose OK.

5. Clickthe 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 youneed 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| Applyto 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| Servicesand find the Pervasive.SQL 2000 Transactional

andRelational 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

andchooseTasks| Restart Pervasive Services.


Windows 2000- The engine can be restarted2 ways:


1. Go to Start| Programs| Administrative Tools| Servicesand find the Pervasive.SQL

2000Transactional and Relational Services.Both services must be stopped and then

restarted inany order.


2. Open the Pervasive.SQL 2000i Control Center, right-click on the Servername and

choose Tasks | Restart Pervasive Services.


Novell/Netware- The engine canrestartedone way:


1. Go to the server console or through an Rconsole session and type in MGRSTOP and

thenBSTOP.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 restartedone way:


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

EnginesandExit.


2. Go toStart | Programs |Pervasive.SQLV8 | Engines| Pervasive.SQLWorkstation

Engineto start theengine.The icon shouldnow appear again in the SystemTray.


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.ForWindows clients,choose either the Microsoft TCP/IP or Microsoft SPXII.


Once these settings have been changed, go to Edit| Applyto save the changes and close the Pervasive Control Center.The Pervasive servicesDO NOThave to be re-started for the client settings to takeeffect.


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 canenable the Pervasive Auto-Reconnect feature.To enable theAuto-Reconnect feature, complete thefollowing steps:


Server


A.In the Pervasive Control Center, click on the Plus sign next to Pervasive.SQLEngines.

B.Click on the Plus sign next to the Server name.

C.Click on the Plus signnext 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 | Applyand re-start the Pervasive.SQL V8 Engines.


Client


A.In the Pervasive Control Center, click on the Plus sign next to Pervasive.SQLEngines.

B.Click on the Plus sign next to theWorkstation name.

C.Click on the Plus signnext 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| Applyto 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 allowthe Microkernel engine to listen forclient connections on all network cards.This is found under the Server|CommunicationProtocols| TCP/IP Multi-homedin the Pervasive Control Center andby default is set to ON for Pervasive.SQL V8.


4.TheTransaction Durability setting isnow 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 toset it to OFF for those releases.

This article was TechKnowledge Document ID:29185