SQL Server Performance

How to implement Database Mirroring with SQL2000

Discussion in 'SQL Server 2005 Database Mirroring' started by ourspt, Nov 14, 2006.

  1. ourspt New Member

    Hi,

    Our client is located in Europe region. Our application was a web based application using SQL Server 2000 database as the back-end, where this server was located in Europe region. All the users will visit this site through out the world.

    Now the client was observing some performance problems in their offices in Asia region. The reason seems to be a relatively bad connection between Europe and Asia. The available bandwidth should be by far sufficient (10 Mbit/s), but the latency seems to be too slow (approx. 350 ms). Our Client is checking with other providers, but they may have similar problems. The effect is that the measured response times in their Asian office are too long (typically 3 – 5 seconds). Their target is to get response times below 2 seconds to make sure that the users can work efficiently.

    One possible solution which has been suggested to us was that to install the web based application also on a server in the Asian office. There would be 2 mirrored databases with the same data. The users in Asia would access this server, whereas the users in Europe and America would access the server in Europe. Probably it would be sufficient to update the data once a day or even less frequently.

    Does SQL Server 2000 support such a solution? Do you think this would be a feasible solution? If this solution should be implemented, how should we proceed?

    Or else Can you suggest any other solution?

    Thanks and Regards

    ourspt
  2. ghemant Moderator

  3. ourspt New Member

    Yes. hemant.

    I need to merge data between both the offices.
  4. ghemant Moderator

    Hi,
    Refer Merge Replication from above link for the resolution of your issue.

    Regards

    Hemantgiri S. Goswami
    "Humans don't have Caliber to PASS TIME , Time it self Pass or Fail Humans" - by Hemantgiri S. Goswami
    ------------------------
    http://hemantgirisgoswami.blogspot.com
  5. satya Moderator

    Database mirroring is not possible in SQL 2000 as it has been introduced in SQL 2005, you have to follow as suggested above. If not log shipping for keeping the databases on warm standby by having a minimal interval of recovery time. If you can afford only Cluster is solution in SQL 2000.

    Satya SKJ
    Microsoft SQL Server MVP
    Contributing Editor & Forums Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing.
  6. MohammedU New Member

    Even if migrate to SQL 2005, database mirroring and log shipping is not an option to your scenario...

    As Hemant mentioned you have Only one option that is Merge replication in SQL 2000 and
    Merge replication and PEER to PEER replication in SQL 2005.

    Mohammed.
  7. satya Moderator

    I wouldn't agree with you Mohammed in this case, Database mirroring comes very handy in such scenario where you can setup.q

    Satya SKJ
    Microsoft SQL Server MVP
    Contributing Editor & Forums Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing.
  8. MohammedU New Member

    I thought OURSPT wants to writable copy at the other end not for DR. If he wnats two way commit then I don't think mirroring is going to work.



    Mohammed U.

Share This Page