by Our one database can have up to 3000 lock timeouts every 20 minutes or so.
It's just one particular database out of 10. Anyway, whenever we do a
select in Enterprise manager the timeout errors start pouring in more than
normal even after the select has finished. The only way we can get the
timeout errors to stop is by manually inserting a record, moving to the last
record in the select result set (again, in Enterprise Manager), or closing
the table. This makes no sense.
We've had this problem before where we can't get control of our databases
until we insert a record or do some other manual data modification to the
table.
Now this doesn't stop all the timeouts but it slows them down.
One other thing: One way to avoid the problem of excess timeout errors is by
issuing the same select statement in Enterprise Manager but with a NOLOCK
hint. Then the timeouts don't increase but still this is no way to deal with
the situation since we still get a TON of timeout errors constantly.
Any help would be much appreciated.