Post reply

Delivering Replicated Transactions

  • December 17, 2008 at 9:23 am

    #195226

    Hi All,

    We updated millions of rows and now my replication synchronization status shows the status as"Delivering Replicated Transactions" , what does it mean, i had 2 subscribers both were showing the same status until one of them is now asking for "initial snapshot" and the other one is still showing the status as "Delivering Replicated Transactions" what does it mean, and why it happened with one, or the other subscription will also ask for snapshot after some time,

    Pls explain what going wrong with it.

    Thanks

  • December 18, 2008 at 9:28 am

    #914671

    It means that the distribution agent is delivering large volumes of transactions and is reporting its status as "Delivering Replicated Transactions". Run profiler on your subscriber (with the appropriate filters, of course) and you'll see that commands are being delivered.

    What's the specific message on the subscriber that's asking for a snapshot? It sounds like the subscription has expired and needs to be resynchronized, but the specific message will help determine that.

    Kendal Van Dyke
    http://kendalvandyke.blogspot.com/[/url]

  • December 18, 2008 at 9:55 am

    #914696

    how can a subscriber get expired. After showing the status like"Delivering Replicated Transactions", the subscriber changed the status to Initial snapshot is not yet available. Can you tell me how this happened.

    Thanks

  • December 18, 2008 at 10:17 am

    #914719

    There are two ways - the oldest synchronized transaction for your subscription has exceeded the value set in the publication (Publication Properties -> General Page) or the value set at the distributor (Distributor properties -> General Page).

    Transactional publications are usually set for subscriptions to never expire in the publication properties but the default at the distributor is 72 hours. If you issued millions of changes it's very possible that your subscription's last synchronized transaction fell behind further than 72 hours which is why it's asking for a snapshot now.

    FWIW, if your millions of changes were done via a stored procedure and you have all the dependent objects at your subscriber you could consider replicating the stored procedure execution....unless you called a stored procedure which affected a single row per execution. 😛

    For more info read the BOL entry for Subscription Expiration and Deactivation

    Kendal Van Dyke
    http://kendalvandyke.blogspot.com/[/url]

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

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