May 6, 2008 at 5:01 am
Hi Friends
In my server i am getting this error could u any body please help how can i slove this error
Table Lock Wait Time Per Second is 997.4150
milliseconds per second, which exceeds threshold of 10
milliseconds per second."
Thanks
kumar
May 6, 2008 at 1:37 pm
You need to reduce your locking.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
May 7, 2008 at 7:21 am
You sure didn't give us much information we could use to help you, but I would start by doing an index analysis to see if you are missing some helpful indexes that would prevent the need for table locks (among several other helpful things proper indexes provide).
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
May 7, 2008 at 7:59 am
Refer to books on line (BOL) sp_who - specifically the entries for columns "blk" and "cmd'
Blk:
The system process ID for the blocking process, if one exists. Otherwise, this column is zero. When a transaction associated with a given spid is blocked by an orphan distributed transaction, this column will return a '-2' for the blocking orphan transaction.
Cmd:
The SQL Server command (Transact-SQL statement, SQL Server internal engine process, and so on) executing for the process.
Run sp_who when the error message is displayed. This information can lead you to learn what is happening then up to you to correct.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply