§Using ‘Standard’ replication achieves much higher throughput performance than using ‘Consolidation’ or ‘Summarization’
- Standard replication can do optimizations such as arraying, commit grouping, etc that can not be performed when using the other replication methods
- Note some optimizations will also be disabled if using Adaptive apply or Conflict Detection & Resolution
§Be aware when you are parking tables/subscriptions
- An inactive (not currently replicating) subscription that contains tables with a replication method of Mirror will continue to accumulate change data in the staging store from the current point back to the point where mirroring was stopped. For this reason, you should delete subscriptions or remove tables that are no longer required, or change the replication method of all tables in the subscription to Refresh to prevent the accumulation of change data in the staging store on your source system.
- The same is true with a parked (idle) table. You need to insure that the replication method is set to Refresh