Abstract 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
Read More »
Yes, post mostly Replication or High Availability topics, but I found this interesting enough to share on my ReplTalk blog. These are the troubleshooting and resolution we used to help a customer explore faster ways to update a 100 million row table. Problem Description Customer was running UPDATE query affecting 100 million rows. This query
Read More »
I hope to answer the question “What is the difference between Push and Pull Merge Replication?” in this blog posting. As you know Merge Replication is all about merging or blending changes between multiple SQL Servers. One SQL Server is designated as the PUBLISHER or “master” copy of the database. Changes made on the Publisher
Read More »
By José Moreira B. Neto Microsoft SQL Server Escalation Services Bounded Update is the term used to describe certain types of UPDATE statements from the publisher that will replicate as DELETE/INSERT pairs on the subscriber. We perform a bounded update for every set based update that changes a column that is part of a unique
Read More »
I recently needed to move a Transactional Replicated table to a new File Group. There are a couple of documented Schema changes that can break Replication. http://msdn.microsoft.com/en-us/library/ms151870(SQL.90).aspx However, I found most problems are solved if I first ensure all data between all peers/subscribers is synched, “no replicated transactions”, before making schema change, then sync the
Read More »