![]() ![]() Microsoft suggests running DBCC Checkdb in odd business hours so that user performance is minimally impacted. For those, I need to mention “it’s higher to possess one thing in situ of nothing”. Some people said they used TABLOCK to avoid I/O overhead of snapshot. If you are using TABLOCK you should have valid reasons like either slow disk system or low disk space. I found my DBCC CheckDB job is running with TABLOCK which cause this issue. So, It’s time to check my code and disk space. However this seems impossible and I do not know why. If hidden database snapshot is not created due to performance reasons or lack of disk space lock request time out period exceeded After a bit of googling the problem I decided to run spwho2 and see what sessions were running. What causes 'lock request time out period exceeded' when droping a column Ask Question Asked 5 years, 11 months ago Modified 5 years, 11 months ago Viewed 18k times 1 I created some columns in our production database but now I need to drop one. ![]() To help prevent a lock timeout from occurring (or to resolve a lock timeout after it has occurred), you can add the custom property ENABLEXARESOURCETIMEOUT on the transaction service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |