Site Sponsored By: SQLDSC - SQL Server Desired State Configuration
Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
The following update statement on 75,000 records runs in 20 sec if I run it from SSMS locally, but > 3 minutes if I run it from SSMS where I've connected remotely.I assumed it would run entirely on server so whether submitted remotely or locally should make no difference.What concept am I missing?
update mytable set LName = '', ssn=null, L4SSN=Null,DOB=null, Address1='', Address2='',City='',Zip='',Email=''
Sachin.Nand
2937 Posts
Posted - 2010-10-18 : 06:55:17
Maybe the network is slow.PBUH
phenreid
Starting Member
29 Posts
Posted - 2010-10-18 : 12:31:34
No,remote connection is over Internet -- supposed to be slow. I think I am missing a concept of how an UPDATE statement works. I thought it simply transmits this tiny one-line statement to the server and executes there and workstation running SSMS just submits it but doesn't do any work. Since it returns nothing, it should run at the same speed whether local or remote and network speed should not matter.I tried it again this morning and it is no longer behaving this way -- runtime are the same. Remains a mystery.