Kbase P16047: What is a good value for RESP_TIMEOUT on DB's of .25G, .5G,
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/12/2008 |
|
Status: Unverified
GOAL:
What is a good value for RESP_TIMEOUT on DB's of .25G, .5G, 1G, 2G?
FIX:
The NO-WAIT option works for DataServer applications in the same way that it works for Progress applications: the DataServer uses a time-out mechanism. If SQL Serverä does not return a record, the DataServer considers the record to be locked. It then cancels the request to the SQL Server and sets the "locked" and "not available" conditions.
During a period of heavy demand, you might encounter situations where the "not available" condition is set although the record is not currently locked by a user. In this case, you might want to increase the time-out interval by using the -Dsrv RESP_TIMEOUT parameter.
So, RESP_TIMEOUT parameter is for situation where traffic or number of concurrent request on SQL Server generates inappropriate behavior on the DataServer.