Create lightweight tables on the subscriber

Find out why indexes or triggers on your subscriber tables will degrade replication performance in this tip, one of 15 tips in 15 minutes.

The following is one of 15 replication tips in 15 minutes. Click here to return to the full list of tips.


4 of 15 replication tips: Create lightweight tables on the subscriber

Any indexes or triggers on your subscriber tables will degrade replication performance. If you have triggers on your subscriber tables, evaluate whether the trigger logic can be incorporated into the replication stored procedures. If your triggers write to audit tables, you can use the NOT FOR REPLICATION clause on the triggers, and they will not be fired by DML performed by a replication process. Then replicate the table on the publisher directly to the audit table.


Click here to return to 15 replication tips in 15 minutes.

About the author: Hilary Cotter has been involved in IT for more than 20 years as a Web and database consultant. Microsoft first awarded Cotter the Microsoft SQL Server MVP award in 2001. Cotter received his bachelor of applied science degree in mechanical engineering from the University of Toronto and subsequently studied both economics at the University of Calgary and computer science at UC Berkeley. He is the author of a book on SQL Server transactional replication and is currently working on books on merge replication and Microsoft search technologies.

This was last published in July 2005

Dig Deeper on SQL Server Database Modeling and Design

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchBusinessAnalytics

SearchDataCenter

SearchDataManagement

SearchAWS

SearchOracle

SearchContentManagement

SearchWindowsServer

Close