Post reply

Sql Server data replication

  • October 27, 2013 at 5:33 pm

    #300470

    Hi,

    We have a database of size around 100GB. We have to replicate this data to a diff company which is in not in our windows domain. We are in central zone they are in pacific zone.

    First we need to load all the existing data into their database and then we have to load data either every day once or it could be real time data transfer.

    What are the best recommended options?

    I am thinking if it's one time a day then log shipping and if it has to be real time data transfer then mirroring. Can we do the real time transfer with transactional replication?

    Is it possible to setup replication/Mirroring to a database server which is not in our windows domain?

    Thanks.

  • October 28, 2013 at 6:14 am

    #1661920

    Hi,

    i think, you can't use you mirroring, because the mirrored database is read only, depends on the version of SQL.

  • October 28, 2013 at 12:30 pm

    #1662135

    Transactional replication will give you near real time updates, but there will be a few seconds delay, depending on how bad the latency is between the two sites. With Mirroring, you will be able to generate snapshots of the secondary database, but that will require an Enterprise Edition license.

  • October 29, 2013 at 11:22 am

    #1662469

    Is it possible to setup replication/Mirroring to a database server which is not in our windows domain?

    Yes but it will be more work to secure.

    We have a database of size around 100GB. We have to replicate this data to a diff company which is in not in our windows domain. We are in central zone they are in pacific zone.

    First we need to load all the existing data into their database and then we have to load data either every day once or it could be real time data transfer.

    What are the best recommended options?

    The two realistic options are Replication (Transaction or Merge) or log shipping. Unless you have someone who is good at replication I would go with log shipping.

    I am thinking if it's one time a day then log shipping and if it has to be real time data transfer then mirroring. Can we do the real time transfer with transactional replication?

    I don't think mirroring is a viable option. Replication will get you as close to real-time as possible but will require more effort than log shipping. Setting up, maintaining, documenting and troubleshooting replication between two time zones (something I have done in the past) can get complicated; especially between dissimilar AD domains.

    My recommendation is to push back against real-time data if possible and setup log shipping; weigh the benefits of the real-time data vs the cost to set it up.

    If it absolutely must be real-time, however, then replication is the way to go.

    "I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

    -- Itzik Ben-Gan 2001

  • November 10, 2013 at 12:13 pm

    #1665347

    SPAM reported.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 5 posts - 1 through 4 (of 4 total)

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