We encounter a problem today with a Distribution Agent failing with “Row Not Found” when pushing an UPDATE to a Subscriber. Reaching the problem we discovered the Subscriber was created using a Backup\Restore from the Publisher and had Identity Columns. The Identity Columns had “Not For Replication” set to NO, which flags the Distribution Agent
Read More »
I came across a great posting by Laurentiu Cristofor [MSFT] called “SQL Server 2005: How to regenerate the same symmetric key in two different databases”. I modified his “column encryption”example slightly to include DecryptByKey and reposted it below. The sample wraps in blog posting but is readable after you paste it into SQL Server Management
Read More »
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 »