13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Initial Programming Considerations<br />

2–42<br />

The NO–WAIT option<br />

The NO–WAIT option works <strong>for</strong> <strong>Data</strong><strong>Server</strong> applications in the same way that it works <strong>for</strong><br />

<strong>OpenEdge</strong> applications: the <strong>Data</strong><strong>Server</strong> uses a time-out mechanism. If MS <strong>SQL</strong> <strong>Server</strong> does not<br />

return a record, the <strong>Data</strong><strong>Server</strong> considers the record to be locked. It then cancels the request to<br />

the MS <strong>SQL</strong> <strong>Server</strong> and sets the “locked” and “not available” conditions.<br />

During a period of heavy demand, you might encounter situations where the “not available”<br />

condition is set although the record is not currently locked by a user. In this case, you might want<br />

to increase the time-out interval by using the -Dsrv RESP_TIMEOUT parameter.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!