November 25, 2007 at 6:19 pm
Hello all,
We are running SQL server 2005 std edition and application which is run in our different centers.
Now the problem is data retrieval is very slow in some centers but acceptable in others from SQL server via VPN.
Our database is not big as well, maintenance which is going on currently is daily transcation log backup, weekly rebuild indexes and database intregrity. currently update statistics maintenance plan is include despite having the option enabled for auto update statistics.
Can anyone make suggestion what more to be done on SQL server or any comments
Thank you
November 25, 2007 at 9:06 pm
Assuming that they are all running the same queries with roughly the same parameters and result set size, SQL probably isn't the issue. Depending on where they are VPNing in from, it could be network issues or perhaps even DNS issues.
November 25, 2007 at 10:59 pm
Yes it is the same queries, all are connected to same database hence same user name, same tables etc
it is very simple layout just delays are giving major headaches and pain
Thank you for the response at least SQL is out of the way now we can concentrate on networking issues
November 26, 2007 at 8:08 am
Since you are running over a VPN I would talk to you're network folks. If your users are at different sites it probably has to do with network bandwidth at their location. That bandwidth as a potential problem can be in the remote users local network or in their pipeline to the internet.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
November 26, 2007 at 3:31 pm
Thanks Rudy
Further I am going to suggest my management to switch the solution to terminal clients which will solve the problem.
if not by VPN
November 26, 2007 at 3:48 pm
Terminal Services will do the trick. Be warned though it can get quite expensive for licensing if you have a large nuimber of users.
If you want to investigate your current issues a bit further you mught want to have a user from each location execute a tracert command from their remote workstation giving the DNS name once and again using the IP address. Whio knows maybe you will find the weak link !
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply