You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running the integritycheck with 'CHECKTABLE' , @tablock = 'Y', a @lockTimeout of 5 and a @LockMessageSeverity of 10. However, when running and hitting a table which is being used I get error 5245 (which is almost the same as error 1222). Since this error is not handled in the stored procedure, it's always returning severity 16 resulting in a failed operation. Am I doing something wrong, or should I classify this as a bug? (using SQL 2022)
Date and time: 2026-04-13 16:35:01
Database context: [DBNAME]
Command: SET LOCK_TIMEOUT 5000; DBCC CHECKTABLE ('[dbo].[TABLENAME]') WITH ALL_ERRORMSGS, PHYSICAL_ONLY, TABLOCK
Msg 5245, Level 16, State 1, Line 1
Object ID 64719283 (object 'dbo.TABLENAME'): DBCC could not obtain a lock on this object because the lock request timeout period was exceeded. This object has been skipped and will not be processed.
Outcome: Failed
Duration: 00:00:05
Date and time: 2026-04-13 16:35:06
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am running the integritycheck with 'CHECKTABLE' , @tablock = 'Y', a @lockTimeout of 5 and a @LockMessageSeverity of 10. However, when running and hitting a table which is being used I get error 5245 (which is almost the same as error 1222). Since this error is not handled in the stored procedure, it's always returning severity 16 resulting in a failed operation. Am I doing something wrong, or should I classify this as a bug? (using SQL 2022)
Beta Was this translation helpful? Give feedback.
All reactions