Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-07-23 : 00:34:00
|
| kevin writes "After putting in a really large query, SQL Server appears to hang.The query I run from Query Analyzer never returns with a result.Once I have done this, I cannot get any new connections to SQL Server either through the Query Analyzer or the Enterprise Manager, becuase they both wait approx 10 seconds before giving an ODBC "Timeout Expired" message.Is it normal behaviour for SQL Server to hang like this. I had assumed that one bad query from one user/connection would be handled better such that other SQL Server users could continue.The only cure is a reboot becuase the SQL Server service will not stop correctly when in this condition. What can I do? If the problem is just with some timeout parameter for new connections, where would I set this? Is there any way to kill off a query once I realise its causing problems? Any server parameters that can be set to kill off these queries? As for the querys I am running, in general its just a great big select with lots of joined tables...something like "select * from this_complicated_view". If I add a condition to the select, then I do get a good result, so the view does work." |
|
|
|
|
|
SQL Servers hangs