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 |
|
MuadDBA
628 Posts |
 Posted - 2003-03-19 : 11:17:41
|
| I have a procedure that warehouses a bunch of data every morning. Occasionally, it runs my SQLServer out of locks. It queries one table with several criteria and inserts it into another table for export.This generates a HUGE spike in my key locks. I get like 30,000 or higher (the table has 400,000 rows). The table has one index, on a field that is not part of the query criteria, and I can't figure out why it uses so many key locks. When I run the same exact query on a duplicate of the DB in test, I don't see the spike....it fires off some page and extent locks, but not nearly as many, and it's done.What should I look at to try to contain this problem?Oh, of course...SQL 7.0 SP3 |
|
|
|
|
|
I am having problems with Key-Level locks....