on 04-25-2013 3:28 PM
We are installing a solution to dynamically replicate all 'insert' and 'update' rows from our 'Production Server' to the 'Archive|History Server';
Our goal is to eliminate the actual 'By Night' Batch Operations.
Three tables on three different Databases are affected by that operation.
On each archiving Database (Replicate), the Tables Definitions are a little different...
For each, we have create a Replication Definition and a Subscription.
Because it is an Archiving Solution, any 'delete row' on Primary Tables should absolutely never be replicated.
We did not find how to replicate just 'insert|update rows' ???
I used to work in an environment with the similar requirement like yours. Instead of implementing changes in repserver, we implement a solution at the archive ASE. We enbale the trigger for replicated ASE and created a delete trigger for each objects. In the trigger , we explicitly issue "rollback transaction" when the user who issue the delete is the maintenance user. It does require a bit of coding if you have lots of tables. Just another method like to share.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.