Hi, folksI have to migrate our company SQL server to Germany. I have new SQL server 2014 installed in Germany and I started to transfer databases and applications. I noticed strange behaviour....I have same database on local SQL and also remote SQL in GE.Login at local SQL and command run from local SQL[b]Insert into DE SQL server – read from local server - tooks 00:01:54[/b]INSERT INTO [DENU00CL0042].ADCList.[dbo].[Company_TEST]SELECT * FROM [dbo].[Company][b]Insert into local SQL server – read from DE SQL server - tooks 00:00:01[/b]INSERT INTO [Company2_TEST]SELECT * FROM [DENU00CL0042].ADCList.[dbo].[Company_TEST]Login at GE SQL, command run from GE SQL:[b]Insert into local SQL server – read from DE SQL server - tooks 00:02:00[/b]INSERT INTO [SKBA1S1846].ADCList.[dbo].[Company_TEST]SELECT * FROM [dbo].[Company][b]Insert into DE SQL server – read from local SQL server - tooks 00:00:01[/b]INSERT INTO [Company2_TEST]SELECT * FROM [SKBA1S1846].ADCList.[dbo].[Company_TEST]In another words PUSH the data and write to other SQL server is more than 150x slower than let the other server PULL the data and write it down. Why? Is any possibility to solve this situation? I also found, that PUSH makes lot of small packets (300) in the WAN network, but PULL is using network packet size of 4096.Many thanxRobert
↧