Database in multi-location

  • Ours is an MNC company with multi-location based production sites.

    We use a workflow management tool which has SQL Server 2000 as backend database & the problem here is that our database is located in the main production site (Site-A) & sub sites users feel the delay in accessing data from the main site through the tool.

    Transaction is continuous & our database size is about 3 GB.

    What would be the best possible option to implement a good solution so that all users can have the same performance and the data duplication is avoided.

  • Hi,

    A couple of things that come to mind

    1. Code optimization - this might not be something you can change if you run proprietory software but check what the application is doing via profiler. Some poorly written code could be returning large result sets back to the application. Make sure queries/procs are as selective as possible.

    2. Upgrade your network - you might need to speak to your network guys to see what traffic is going out through your WAN. Packet shaping might be an idea if SQL server is contending with email traffic etc.

    3. Look at using Citrix - I found this to be a good solution for really remote sites that have poor link speed. Citrix allows your application to run on a central server close to your SQL database.

    Hope some of these might help.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply