February 9, 2009 at 7:32 pm
I'm trying to maintain 2 copies from my production db. One is a warm backup using continuous transactional replication so it applies deletes along with everything else-- so not a problem.
The other copy is a historical copy were I want to copy old data then delete it off the production db. This has got to be a common scenario but I'm wondering whats the best way to do it.
Using replication, it'll delete the historical rows when I delete them from the prod db-- is there a way to turn off the deletes?
I tried DTS with not dropping tbls first and append only but it still looks like its zeroing out the row counts and processing the entire production db each time-- not very efficient.
Or is this a "write your own script" scenario?
tks
February 9, 2009 at 10:27 pm
You need some way to determine what's changed.
I might actually write triggers on the first copy that moves inserts and updates to a second database. Then the deletes won't affect things, and production isn't moving the data twice.
February 10, 2009 at 8:25 am
You can turn off replication of delete statements. Check out this blog post by Kendal Van Dyke:
http://kendalvandyke.blogspot.com/2008/12/hey-i-said-not-to-replicate-delete.html
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
February 10, 2009 at 9:06 am
cool. I assume that's in sql 2000 also. I'll hunt around for it. It didnt jump out at me.
tks for the pointer.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply