![]() It might also help to use forceliterals on those queries to eliminate a poor cached plan from causing repeated deadlocks, but I won't try that unless the specifying the index fails to resolve the issue. The more appropriate index by far for these delete_from statements it the TTSDimIdx, since the where clause specifies the PARTITION, DATAAREAID, and TTSID. 09:45:54.41 spid10s waiter id=process4fee8a7848 mode=U requestType=wait 09:45:54.41 spid10s waiter id=process1e1d088 mode=U requestType=wait Here is a snip from my own SQL Server ERRORLOG from today showing the deadlock type keylock on the I_2397RECID index. ![]() Here is a good article that got me on the right track to hopefully fixing this problem.Ī/./locking-on-the-inventsumdelta-tableĪ/./locking-on-the-inventsumdelta-table-additional-tweaks This looks to be related to statistics on the InventSumDelta table which causes SQL Server to select the wrong index, i.e. nvarchar(21))UPDATE SALESPARMLINE SET WHERE AND AND AND AND 17:06:40,spid27s,Unknown,inputbuf 17:06:40,spid27s,Unknown,waiter id=process2ab62077c28 mode=U requestType=wait ![]() 17:06:40,spid27s,Unknown,waiter id=process2ab6207fc28 mode=U requestType=wait ![]() ![]() Line number: 0,0000000000.ĭeadlock, where one or more users have simultaneously locked the whole table or part of it. Hi, i have deadlock problem in SalesParmLine when concurrent users trying to Post sales invoice through web services.Ĭannot edit a record in Sales order line - update table (SalesParmLine). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |