Sometimes, this issue could happen to performance issues. If you deem that query inconsequential, then you can kill it using kill .Once you identify this, you can use dbcc inputbuffer (spid) to find out what query/command it is doing that has taken a lock on this table. ⢠Finally, after this 10 seconds we are going to receive this error message meanwhile we don't execute the commit transaction of the execution of CREATE TABLE. select from sysprocesses where spid .Following our article here: Lesson Learned #22: How to identify blocking issues? - Microsoft Community Hub you could find the blocking issue: As sys.tables is now blocking by a previous CREATE TABLE instrucction we have to wait to release this blocking.By default it uses repeatable.read, but you can change this in the config. To do this it takes a lock on the database, and it looks like this is failing: SQLServerException: Lock request time out period exceeded.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |