Have seen this many times over the years. Wondering if there is a simple solution now, since we have governors, etc.
When you are bringing tables from other servers ....
select * into myTable from remoteServer..myTable
...I guess, the machine first checks to see if there is a table called myTable .... then starts creating first and then brings in the rows. I believe, at the beginning of the process, it locks some resources which includes the sysobjects table... and it does not get released until it brings it all the rows from the remoteServer..myTable and finishes the transaction and releases everything/sysobjects.
Did other people experience this... you cannot query the sysobjects table intermittently while the tables are being pulled in.
Is there a remedy for this? ....set nocount on, etc ......
It just bugs me.
