Pull Subscription Expiration

  • If I have a server that I keep synced using a Pull subscription (transactional replication), how long can I have the distribution agent stopped before I have to resyncronize using a snapshot/restore? Does it queue up the pending transactions in the distribution database, then send them across when the agent is restarted?

    Finally...Is the value set in the Publication-->Subscricption Expiration (hours) the amount of time that transactions will be queued before the pull subcription need to be reinitialized?

    Thanks.

    -Dan


    -Dan

  • I think distribution database keeps track of transactions that are processed by distribution agent. So, as you suggest, the distribution agent will queue up all the trasactions and then send them once the Distribution agent is restarted.

    I always thought that the value in Publication-->Subscricption Expiration is the amount of time after which the subscription is dropped if synchronization has not yet occured.

    Might want to check me on these...

    Alek

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

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