Post reply

Replication pre-requisties

  • August 8, 2013 at 10:40 pm

    #276740

    Hi All,

    I am going to set up replication in an OTLP environment. I would like to know what as a DBA should i check before setting up replication.

    Last time, when I set up replication in such an environment, i got memory issue and SQL Server started generating memory dumps.

    I had to remove replication temporarily. Please let me know if there is way to determine the memory required for replication.

    thanks,

  • August 9, 2013 at 12:50 pm

    #1640246

    Hi,

    Any information will be helpful..

    Thanks,

  • August 9, 2013 at 2:06 pm

    #1640275

    First, check out the Stairway to SQL Server Replication[/url] by Sebastian Meine.

    I am going to set up replication in an OTLP environment. I would like to know what as a DBA should i check before setting up replication.

    I personally like SQL Server Replication but setting up and maintaining it is not trivial task; replication is easy to break and can be difficult to fix. There are a number of architectural and security considerations to address before implementing replication. The very first thing you should ask is if replication is the right option.

    Sometimes Replication is overkill and you can do the job with just using scripts, triggers, SSIS, the a SQL agent, etc...

    That said, if you have done your homework and determined that Replication is the right choice then some questions you should be asking is:

    1. What do you need to replicate? What data do you want to make available and to whom?

    2. What objects need to be replicated (tables only? triggers? Views?)

    3. How often does this information need to be updated

    4. Will the replication be occurring on only one instance? across multiple instances? one-way? two-way?

    5. What will be your recovery strategy if your replication breaks? Becomes slow?

    After you have answered these kinds of questions you need to determine what kind of replication: Snapshot, Transactional, Merge...

    These are the things you need to "check" before setting up replication.

    Last time, when I set up replication in such an environment, i got memory issue and SQL Server started generating memory dumps....

    I had to remove replication temporarily. Please let me know if there is way to determine the memory required for replication.

    It depends :hehe:. Replication is nothing more (really) than some bonus SQL executables that sets up SQL objects such triggers and stored procs, SQL agent jobs, etc... You need as much memory as is required to accommodate triggers, run stored procs, execute SQL agent jobs....

    "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

  • August 9, 2013 at 2:15 pm

    #1640276

    Your question is to too general to give you specific advice. Replication can have so many different topologies, design goals and performance requirements it is not logical to provide recommendations without more information.

    The probability of survival is inversely proportional to the angle of arrival.

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

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