Q
Problem solve Get help with specific problems with your technologies, process and projects.

Replicating between vendor's database and own instance

I'm considering implementing replication between a vendor's database and one of our instances. We share a common table they would use to send records to us and we, in turn, to them. We would subscribe (horizontal) to rows they INSERT and they to rows we INSERT. In essence, this is a sort of message queue. All this is doable with replication as I understand the feature? If we define a trigger on our table in order to process new records, will that trigger fire when the Replication Engine inserts a replicated record in our table?

Yes, it is doable. The replication engine is issuing transaction, just as any other application would. So, yes,...

it will cause triggers to fire. If you wish to suppress triggers from firing when the replication engine is applying transaction, then you would add the "not for replication" option to the trigger.

For More Information

This was last published in June 2003

Dig Deeper on SQL Server Replication

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchBusinessAnalytics

SearchDataCenter

SearchDataManagement

SearchAWS

SearchOracle

SearchContentManagement

SearchWindowsServer

Close