Home Forums SQL Server 2005 SS2K5 Replication Performance Expectations w/ Transactional Replication RE: Performance Expectations w/ Transactional Replication

  • November 6, 2009 at 9:37 pm

    #1076226

    Ian Scarlett (11/6/2009)

    Jeff Moden (11/5/2009)

    Most of it is all very, very fast because it uses BCP behind the scenes.

    Are you sure, Jeff?

    I know the initial snapshot uses BCP, but (unless it's changed radically since SQL 2000), I thought the transactions were then reconstructed as individual insert/update/delete statements for application to the subscriber. It replicates "transactions" (usually involving > 1 table), and therefore has to apply the changes in the same sequence they were done on the publisher.

    Heh... I was until you said that... I've got to double check but I believe you're probably right... thanks for the catch.

    --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)