May 19, 2009 at 4:15 am
Hi,
We are in the process of optimising our import process. The solution being tested is that we import into small staging tables and then replicate the data from those tables into the main live tables when we are ready. The way we do this is to import the unique transaction reference ID as a negative of itself (i.e. -100 instead of 100) and then programmatically update a certain number of these to be positive and allow replication to move the data (a filter is on the replication where the transaction ID > 0).
This works great and is a lot faster. However, we now have the issue of removing the data from the staging tables. The idea was to update the transaction IDs to be -1 (thus out of the scope of replication) and then delete them. However the replication is picking update and then the delete.
Is it possible to set up the replication to not replicate the delete statements? That way we could just delete the data once its been processed. I know I could alter the replication SPs, but I am hoping there is a better way of doing this?
Thanks in advance
Tom
May 19, 2009 at 5:23 am
Hi,
Did a bit more research and it was quite a simple fix in the end... Just amended the publisher properties > articles to not replicate delete commends...
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply