June 17, 2008 at 12:43 pm
Hello
I have a job that runs UPDATE STATISTICS on various tables of a database during the night. This morning it was still running when I got into the office. After a few investigation, I found out that there was an [UPD-STATS] lock held by another spid, on a table with a little less than 30 000 rows
From what I've found so far, this lock is caused by auto update statistics (which is on at the database level). The lock is still being held, after more than 14 hours. Anyone have any idea why this lock is not yet released?
There are no other [UPD-STATS] in syslockinfo, and from a trace I can see that the spid holding it is regularly executing various queries (using sp_cursorexecute so I cannot say what those queries are). That spid is used by a Siebel application, so we're not sure if we can kill it without causing other problems
@@version : Microsoft SQL Server 2000 - 8.00.2187
June 17, 2008 at 1:39 pm
Hi,
I haven;t heard of this before in sql server.
I think upd_stats would be the name of some utility which might be doing something in the db (just a guessing)
subban
June 17, 2008 at 3:01 pm
You should probably contact Sibel support. I think you are probably changing the table too fast and auto update stattistics is triggered on each invocation OR the app is actually issueing the update statistics statement repeatedly.
* Noel
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply