Year: 2010

All about “Identity Range Management”

José Moreira Neto | SQL Server Escalation Services Automatic Identity Range Management Microsoft SQL Server automatically generates sequential numbers for new rows inserted in the table containing the identity column. Identity columns are normally included as part of Primary Keys, therefore the need to avoid duplicates. To use identity columns in a replication topology that
Read More »

Navigating SQL Replication SubscriptionStreams setting

Rishi Maini | Microsoft SQL Escalation Services This blog posting discusses the new Distribution Agent SubscriptionStreams parameter.  This option reduces the latency when moving data from Distributor to Subscriber by using multiple parallel writer threads.  For more information on Replication “threads” see Transactional Replication Conversations blog posting. From SQL Books Online (good place to start)
Read More »

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 »