March 9, 2009 at 2:53 pm
I have one table replicating from one db to another on the same server.
The replicated table in the replicating db is cleared by a trigger fired on the table in the replicated db.
The subscribing db is now moving to a different server. Do I have to modify my trigger to go across servers to delete the rows from the replicating db or is there a part of Transactional replication that allows replicate then delete.
Replicate from A.Table to B.Table & delete all rows in A.Table.
March 10, 2009 at 4:01 pm
Can you tell us why are you replicating in the first place?
Why don't you write directly to the "replica" table, that way you don't need replication at all 🙁
* Noel
March 11, 2009 at 9:54 am
For some reason when I try to write directly in a different db, the $#@%!#$% ERP blows up.
I have a trigger in the ERP database that fires to send rows to a table so MSDS' are generated in the MSDS db.
So, when the trigger fires it writes to a table in the ERP db & then replicates to the table that needs to be written to in order to generate an MSDS.
Now the gotcha for me is the replicated table has rows picked up by the MSDS system & then clears the replicated table, therefore, rendering my deleting rows from the published table.
Hope this makes sense, or anyone knows of another way that would make more sense.
Thanx!
March 11, 2009 at 1:50 pm
1 correction.....
When the trigger fires it writes to the table of the ERP database & then replicates to a different db, because ERP blows up if I try to write directly to a different db.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply