Kbase P37596: Which Broker Should I place the -SQLStack, -SQLStmtCache, and -SQLCursor parameters?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/4/2011 |
|
Status: Verified
GOAL:
Which broker should SQL Server parameters be added to?
GOAL:
Where to place -SQLStack, -SQLStmtCache, -SQLCursors, -SQLTempBuff, -SQLTempDisk, -SQLTempPgSize parameters?
GOAL:
Can new values for -SQLStack, -SQLStmtCache, -SQLCursors, -SQLTempBuff, -SQLTempDisk, -SQLTempPgSize be defined on start of secondary login brokers?
GOAL:
If using multiple database brokers, which broker should have the SQL parameters?
FACT(s) (Environment):
Progress 9.1D
Progress 9.1E
OpenEdge 10.x
All Supported Operating Systems
FIX:
The -SQLStack, -SQLStmtCache, -SQLCursors, -SQLTempBuff, -SQLTempDisk, and -SQLTempPgSize parameters should be defined on the primary broker startup.
All brokers and server processes which are subsequently started from that point forward will inherit the value defined under the primary broker.
All SQL server processes which are spawned will have their own private stack, statement cache and cursors allocated based on the values defined in the primary broker.
These values are not shared across all the SQL servers, rather they define specific values for each SQL server spawned.
Example:
If -SQLStmtCache 500 were defined on the primary broker and 10 SQL servers were spawned each would have a separate set of 500 statements it could cache.