You can time out the query, but I would find out why you are having the
problem first.
Step 1 is to run performance counters and see what is happening
Then, you will likely find out which queries are your problem child and fix
them. Followed by possibly adding or correcting indexes. Or moving to a
stronger box, as you have outgrown the box you are running SQL on.
Throwing in the connection timeout will let you tell the user the server is
too busy, but it will not solve the problem.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
|
*************************************************
"Microsoft Newsserver" <me@nowhere.comwrote in message
news:OT**************@TK2MSFTNGP06.phx.gbl...
Hi,
We have situations occasionally where the SQL server is extremely slow to
respond. The problm is that the user is left with loading page and has no
idea what in heaven is going on.
Does anyone have any ideas how the DAL can be confiured to timeout and
throw an exception if the response is not quick enough ?
Cheers