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 - 2000-10-17 : 16:41:14
|
Charlie writes "We have "The Application from Hell" written in Access 97 that stores its data in SQL 6.5 via linked ODBC tables.
The problem that we have happens when a user forgets to log out at the end of the day. The DBCC process' that the server runs at night get blocked by Access' connections.
Access' select statements are incomplete due to it only prereading, (I think), 1000 rows at a time. Thus, they leave a table intent lock on the tables they’re selecting from, and this blocks the DBCC checks from grabbing the exclusive locks they need to run.
In the morning users can't log in until someone goes in and manually kills the blocked connections...
The KILL statement is doesn't work because the blocking SELECT processes are still shown as active, and do not respond to KILL
Is there a way to kill these connections automatically??????" |
|
|
|
|
|
How do you automatically kill connecitons w/ table intent locks?