It's highly unlikely that it was clashing with another transaction, as the system was brought down for the update. This wouldn't be the first time we've run into. If you're on the latest version, and you're still experiencing the error, that means SQL Server isn't honoring isolation level requests in the DMVs. This issue was reported and fixed over a year ago in this Github issue. Any thoughts or ideas would be appreciated. Error using Alarm Action Execute a SQL Script: 'Lock request time out period exceeded.' (4302610) Return Title Error using Alarm Action Execute a SQL Script: 'Lock request time out period exceeded.' Description The Alarm Action Execute a SQL Script action is used to execute a script. Make sure you're on the latest version of spBlitzWho. I ran it on another database where the number of rows is smaller (~20m)and it ran just fine. INNER JOIN RealTable ON RealTable.PrimaryKeyID = #Update.PrimaryKeyID I_ID int PRIMARY KEY NOT NULL IDENTITY(1,1), Here is the pseudo code: BEGIN TRANSACTION Tried to run the script two times now, the first time it broke after updating roughly 17m rows, the second time it stopped at 14m.Įrror message: Msg 1222, Level 16, State 43, Line 122 The Lock request time out is set from the client application in your case EM. To resolve this behavior, use one of the following methods: Click to clear the Override connection string time-out value for table designer updates check box for the table designer and for the database designer in SQL Server Management Studio. The updated is broken in batches, with checkpoints to allow clearing the transaction log. I'm running long bulk update script which is updating ~50m records. I tried to find something similar, but couldn't so decided to ask directly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |