Is the problem replicated at the hq/head office? Because if its still slow there then the bandwidth issue may not be the concern.
Then, on report generation, where is the reporting done? Are u using stored procedures? Though unlikely, it could be that the logic is in the vb app as opposed to it running on the SQL server.
My advice, as has been noted by other listers:
a) Check your queries. For shared db some reports dont have to be regenerated for every user
b) Check your network. If the reports are generated fast enough, then its the serving thats the problem
c) Maybe the application/platform itself
On Tue, Nov 29, 2011 at 10:12 AM, muskiv
<kulebak@gmail.com> wrote:
Aki
On Tue, Nov 29, 2011 at 11:05 AM, aki
<aki275@gmail.com> wrote:
@muskiv, imo, your problem is purely on the network layer. You need to see the number of db sessions open in tcp to understand the overhead demanded by the client-server wan-wan application.
Sorry how do I do this in WIN2K3?
You way eventually have to install wan application and optimization accelerators since increasing the bandwidth on the remote sites would not justify costs.
Same question as above. (Sorry I know I can google :)
Have you also done local LAN tests on the seutp to determine the nbottlenecks at DB or hardware level?
A number of LAN tests have been done. I've noted a few that I think need resolution...work is in Progress. Just didn't want to miss anything
Thx
_______________________________________________
Skunkworks mailing list
Skunkworks@lists.my.co.ke
------------
List info, subscribe/unsubscribe
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke