January 27, 2018 at 9:43 pm
Hi guys,
I'm using an app that utilizes sql 2014. When I'm using the app on LAN, it's obviously working fast, but over WAN, things take 3 to 5 times longer all around. There are certain times where the client app will make like 5 queries in a row w/ stored procedures if I'm not wrong, and that takes it like 5 whole seconds, when LAN is about 0.75 seconds for the same task. It seems to me that it has to establish a connection on each of those calls due to the way the app is programmed (if i'm not wrong, that is).
I can obviously use remote desktop in windows to connect remotely and work that way, and it's fast in that case, but there are drawbacks to this as well.
Anyhow, I can't edit the application, as I'm not the one who designed it. I was hoping for some tips on getting things faster. Are there any possible settings that might be hindering TCP remote connections in SQL server, as far as speed might go?
Thanks for the help in advance,
Dave
January 28, 2018 at 11:12 am
fesliyanstudios - Saturday, January 27, 2018 9:43 PMHi guys,I'm using an app that utilizes sql 2014. When I'm using the app on LAN, it's obviously working fast, but over WAN, things take 3 to 5 times longer all around. There are certain times where the client app will make like 5 queries in a row w/ stored procedures if I'm not wrong, and that takes it like 5 whole seconds, when LAN is about 0.75 seconds for the same task. It seems to me that it has to establish a connection on each of those calls due to the way the app is programmed (if i'm not wrong, that is).
I can obviously use remote desktop in windows to connect remotely and work that way, and it's fast in that case, but there are drawbacks to this as well.
Anyhow, I can't edit the application, as I'm not the one who designed it. I was hoping for some tips on getting things faster. Are there any possible settings that might be hindering TCP remote connections in SQL server, as far as speed might go?
Thanks for the help in advance,
Dave
The most likely cause for this is returning too much data to the client app. Not much you can do about that other than buying a bigger/faster network pipe. Another possibility is excessive chattiness, which is mostly a factor of latency. Again, faster network is likely the only fix.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
January 29, 2018 at 3:52 am
This was removed by the editor as SPAM
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply