Follow the Data in Transactional Replication
Microsoft SQL Server Escalation Services
Many technology solutions use a STORE and FORWARD model to move data though out the business. It begins when source data change is detected, collected, and STORED in a cache. This cache data, often on a schedule, is processed and FORWARD to one or more destinations. Microsoft technologies using “store and forward” include Log Shipping, Database Mirroring, Transactional Replication, Merge Replication, Change Data Capture, Change Tracking, Sync Services, SSIS ETL packages, and SQL Azure. As we “Follow the Data” for Transactional Replication, look at the players, their roles, auditing options, supportability features, and ability to handle changing business needs.
Store and Forward in Transactional Replication
In Microsoft SQL Server Replication technologies “Store and Forward” model is called Publish-Subscribe. In this paper I’ll cover techniques used by Microsoft SQL Server Transactional Replication for moving data throughout a topology. Topics covered include Roles, Jump Start, What’s Normal, Auditing, “NOT” Replicated, Really Big Batches, Open Transactions, Do Over, Divide-n-Conquer, Cleanup, and Supportability, can be applied to many technologies using similar “Store and Forward” methodology to move data throughout an organization.
The attached PDF document contains the entire paper.