Large SQL update effect on SQL2005 transactional replication

  • I'm a newbie to Replication and recently setup the following. 

    Publisher and Distributor on the same SQL2005 server, then I've got 7 subscribers(SQL2000 servers) and I'm using push subscriptions.  I'm replicating 5 SQl tables which don't have too many changes and these are scheduled to run every 3 hours.   In a few days a large one off SQL update with add an additional 10,000 rows to one of the replicated tables.   I was wondering what impact this would have on the above setup i.e are there any sort of limitations here.  I'm assuming not but thought I would check.  I'm thinking it will just cause additional overhead on the server, but the update is being applied when no users will be using the database. 

    Any feedback greatly appreciated.

    Thanks

     

  • Large updates *do* have impact on replication. The reason is that whatever goes into your transaction log gets stored in the distribution database (for the retention period). 10 000 rows is *not* a big deal for my current servers but it could be for a not very performant one.

    Just make sure that you have enough space to house that info in the distribution database. Other than that you should be "fine"

    Cheers,


    * Noel

  • Your transaction log will not be truncated until the transactions are replicated to subscribers so there is a chance of growing tlog...

    As long as you have free space there is no problem...

    MohammedU
    Microsoft SQL Server MVP

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

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