Triggers on replicated SQL-server database
Posted on 2013-01-21
I am using sql-server 2005. My setup is like this:
Server A ----> Server B.
Server A is replicated to server B synchronously. (No data needs to come back from server B) I am using the built in transcription replication.
I have written triggers that need to fire when data is modified on Server A. I only need to read the data generated by these triggers on server B.
The triggers involve some complex views and will be quite taxing on server A. Server A is mission critical, server B is not. I want there to be minimal impact on Server A.
Is it possible to have triggers fire on Server B when the transactions from Server A change things, as opposed to have them fire on Server A when the tables are first modified?
a. User modifies table x on Server A.
b. an update to table x causes a trigger to fire which records data in table y.
c. Server A replicates the data in table x and table y to server B.
a. User modifies tabel x on Server A.
b. Server A replicates the data in table x to server B.
c. An update trigger on Server B fires when it detects that the replication transaction has changed the data in table x.
d Server B records data in table y.
I want Scenario Two, can it be done?