Post reply

SQL Server Database Replication. URGENT PLEASE

  • April 28, 2012 at 1:02 am

    #273421

    Hi,

    I hope everybody is doing well.

    I have two Windows Server 2003 Servers. On both servers, we have installed same application and SQL Server 2008 database. Both servers are located in different locations and they can ping each other. I have 500 GB in other location for storage, but currently I am not using that storage.

    I have to use one server for production and other server for disaster recovery.

    Application will update the database which is located in production server. I want to update same database in other database which is located on other server which is used for disaster recovery.

    Please help me. I have to implement it ASAP.

    Your proper and valuable reply will be highly appreciated.

    Thanks in advance.

  • April 28, 2012 at 1:24 am

    #1480815

    fmaruf (4/28/2012)

    Hi,

    I hope everybody is doing well.

    I have two Windows Server 2003 Servers. On both servers, we have installed same application and SQL Server 2008 database. Both servers are located in different locations and they can ping each other. I have 500 GB in other location for storage, but currently I am not using that storage.

    I have to use one server for production and other server for disaster recovery.

    Application will update the database which is located in production server. I want to update same database in other database which is located on other server which is used for disaster recovery.

    Please help me. I have to implement it ASAP.

    Your proper and valuable reply will be highly appreciated.

    Thanks in advance.

    I think you should use "Transactional replication". The following link will give you an idea for you to choose for yourself.

    SQL Server database replication

    Vinu Vijayan

    For better and faster solutions please check..."How to post data/code on a forum to get the best help" - Jeff Moden[/url] 😉

  • April 28, 2012 at 2:53 am

    #1480818

    Thanks for your reply.

    But I want to move the database storage from local to central storage.

    Please advice.

  • April 28, 2012 at 3:12 am

    #1480819

    But I want to move the database storage from local to central storage.

    Can you please explain more on that? What exactly you have in your mind?

  • April 28, 2012 at 3:15 am

    #1480820

    vinu512 (4/28/2012)

    fmaruf (4/28/2012)

    Hi,

    I hope everybody is doing well.

    I have two Windows Server 2003 Servers. On both servers, we have installed same application and SQL Server 2008 database. Both servers are located in different locations and they can ping each other. I have 500 GB in other location for storage, but currently I am not using that storage.

    I have to use one server for production and other server for disaster recovery.

    Application will update the database which is located in production server. I want to update same database in other database which is located on other server which is used for disaster recovery.

    Please help me. I have to implement it ASAP.

    Your proper and valuable reply will be highly appreciated.

    Thanks in advance.

    I think you should use "Transactional replication". The following link will give you an idea for you to choose for yourself.

    SQL Server database replication

    These might help in this case:

    Create a Central Management Server and Server Group

    Central Management Server by Brent Ozar[/url]

    Vinu Vijayan

    For better and faster solutions please check..."How to post data/code on a forum to get the best help" - Jeff Moden[/url] 😉

  • April 28, 2012 at 3:33 am

    #1480823

    Central Management Servers are not HA solutions.

  • April 28, 2012 at 3:38 am

    #1480824

    I want to store data on central server.

    Application from production server should update that data

    Both servers should access that data.

    Please note, both servers will be on different location.

  • April 28, 2012 at 3:38 am

    #1480825

    fmaruf (4/28/2012)

    Application will update the database which is located in production server. I want to update same database in other database which is located on other server which is used for disaster recovery.

    If you want a solution for near real time business continuity and you want to implement rapidly you should be looking at mirroring. If you can take small lag in and potential loss of data, logshipping could be useful.

    fmaruf (4/28/2012)

    Thanks for your reply.

    But I want to move the database storage from local to central storage.

    Please advice.

    Are you talking about moving away from "direct attached storage" to a SAN? In which case you need to speak to your system engineer if the drives arent attached.

  • April 28, 2012 at 4:02 am

    #1480828

    Thanks MysteryJimbo

    Yes you are right

  • April 28, 2012 at 4:07 am

    #1480830

    Please google for SQL Server Clustering with geo-clusters. It has few limitations / requisites & would be a costly solution.

  • April 28, 2012 at 4:15 am

    #1480832

    fmaruf (4/28/2012)

    I want to store data on central server.

    Application from production server should update that data

    Both servers should access that data.

    Please note, both servers will be on different location.

    Will the data need updating on both servers?

    If so, merge replication or peer to peer transactional replication could work and will be much less costly than a Geo Cluster. It would also potentially be implemented in days rather than weeks.

  • April 28, 2012 at 4:21 am

    #1480833

    Per BOL:

    If the cluster solution includes geographically-dispersed cluster nodes, additional items like network latency and shared disk support must be verified. The entire solution must be on the Geographic Cluster Hardware Compatibility List.

    More: http://msdn.microsoft.com/en-us/library/ms189910(v=sql.105).aspx

Viewing 12 posts - 1 through 11 (of 11 total)

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