Snapshot Publication is not allowing cleanup of the distribution database


in setup have both transactional publications , snapshot publications. understanding snapshot publication not track or care transactions occured since last sync. every execution of sync deliver existing snapshot, snapshotting operation takes data out of tables.
problem code in sp_msmaximum_cleanup_seqno considers last transaction delivered each of distribution agents found in msdistribution_agents. includes distribution agent delivers snapshot. therefore, distribution database accumulates transactions between executions of snapshot+sync operations.

see it, have missed configuration option. otherwise, seems option modify sp_msmaximum_cleanup_seqno or similar circumvention of tracking occurs.


suggestions solutions?

even though snapshot agent shut down, log reader agent continues delivering transactions distribution database. these transactions delivered subscribers distribution agents running transactional publications.

problem not snapshot agent itself, or snapshot replication. problem how transactions being accumulated , (not) cleaned through interaction between snapshot replication, transactional replication , code in sp_msmaximum_cleanup_seqno

have gone through code of , can see going on. sproc responsible returning recent transaction can cleaned up, can return transaction number (binary) delivered snapshot publication distribution agent. and, in situation that. given snapshot publication configuration (that creates , distributes snapshot) runs less (once week), transactions have occured since then, being accumulated in distribution database. under normal scenario these transactions cleaned out since have been replicated transactional publication distribution agents.


SQL Server  >  SQL Server Replication



Comments

Popular posts from this blog

more indexes

ActiveDirectory

Virtual Channel