What is the best generic approach re-setting timeouts on SQL commands/queries ?
Using MS SQL Server 2000,ADO, TADODataSet.CommandTimeout etc. (if it matters)
If command's timeout setting is too short and data volume is large, some queries
get cancelled because of a timeout error.
However if command timeout setting is long, but there is say a loss of DB
connection or some other unrelated to data volume error, then user/application
have to wait for the whole duration of command timeout setting just to find out
about this connection loss for example.
In other words short command timeout settings do not allow some queries to
complete whilst long command timeout settings may cause long unnecessary delays
before unrelated to volume of data errors are reported.
What is the optimal approach you think ?
Regards
Alex
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
