LogReader fails with Cannot execute as the database principal because the principal “dbo” does not exist

LogReader fails with error 15517: 2010-02-25 21:16:35.054 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'CHRISSKACER'.'. 2010-02-25 21:16:35.056 The process could not execute 'sp_replcmds' on 'CHRISSKACER'. 2010-02-25 21:16:35.057 Status: 0, code: 15517, text: 'Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot
Read More »

Decrypting @schema_option parameters binary value for a Transactional Replication Article

Balakrishnan Shankar | Microsoft SQL Server Escalation Services During the course of troubleshooting, Microsoft SQL Support team we collect from customers the Publication Creation Script. In cases involving Snapshot generation and application problems, it might become necessary to decrypt the schema options for an article from customer’s script. Below script will help deduce that. The
Read More »

Reinitialization MS SQL Replication Subscirber may cause data loss

In Transactional Replication Subscriber reinitialization instructs the Distribution Agent to locate and distribute a NEW Snapshot to the Subscriber.  In Merge Replication, the reinitialization is done by the Merge Agent. Depending on the Replication settings, the Subscriber tables may either be 1) dropped, deleted, or 3) truncated resulting in loss of data on the Subscriber.
Read More »

All about “Not for Replication”

Rishi Maini | Microsoft SQL Server Escalation Services All about “Not for Replication” “Not for Replication” is a property which can be set for different objects like Check constraints, Foreign Key constraints, Triggers , Identity columns etc while using SQL Server Replication. Feature used when the DBA would like the transactions to behave differently when
Read More »