July 30, 2015 at 9:56 am
We see this happen when executing a SELECT INTO with an OPENQUERY
[font="Courier New"]SELECT ... INTO tablename FROM OPENQUERY(linkedserver,'sql statement')....[/font]
The workaround we have found is to use a global temp table for the target of the INTO, as in
[font="Courier New"]SELECT ... INTO ##globaltemptable FROM OPENQUERY(linkedserver,'sql statement')....[/font]
and then we copy from the ##globaltemptable to the tablename
August 27, 2015 at 7:50 am
I realize this is an old post but you can run sqlcmd -S server -d database -Q"sp_who2" -o mywho2.txt
August 28, 2015 at 1:57 am
"Lock request time out period exceeded." can appear during expanding of nodes, if the master database is locked.
It seems like the Management Studio does not use "WITH (NOLOCK)" when reading this tree from the master database.
Such a lock of the master database can happen, if DDL commands are used on objects in any database taking a longer time (maybe because they are used within a Transaction/Commit block). Even a TRUNCATE statement uses DDL internally, actually recreating the table in the background.
Using Traces, you might be able to find out, which processes might have caused that lock.
November 20, 2015 at 12:53 pm
Hello,
I ran into this issue when an uncommitted transaction caused the error message. Manually committing the transaction solved the error. Please consider using DBCC OPENTRAN to identify open transactions that may need to be committed, or as a last resort, killed.
I hope this is helpful!
DBCC OPENTRAN -- https://msdn.microsoft.com/en-us/library/ms182792.aspx
COMMIT TRANSACTION -- https://msdn.microsoft.com/en-us/library/ms190295.aspx
Additional Research -- http://www.dotnetlearners.com/blogs/view/3/MS-SQL-Query-to-find-and-remove-uncommitted-or-open-transactions.aspx
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply