July 27, 2006 at 8:37 am
Hey - I know that there is a replication forumn, but since I have more of a question as how to handle this administrative task, I figured here would be the ideal place.
Here is the situation I have. We have a number of DB's that have a relitively high number of updates / inserts (I want to say about 1 mil a day some days), and the reporting that gets done there can be slow, as they are doing a lot of table scans (I know - thats the next project I will take on), the plan was to archive older records off the box, and having them placed on some sort of warehouse. I was thinking transactional replication, but as I looked at it more, it looks like when a record is removed from the primary, it will remove that record of the subscriber. What we want is to keep a certain date range (like 45 - 90 days) on the primary, and 7 years on the secondary server.
I have also thought about making some sort of manual replication...
Please let me know your thoughts / experiences
Cory
-- Cory
July 27, 2006 at 8:46 am
Sounds to me like what you need is a nightly job to handle this. Run a DTS package to move over the new records / update changed records and then run a stored procedure or two to do cleanup.
At least, that's how I'd do it...
July 27, 2006 at 9:12 am
Yep,
I'd agree with Pam. DTS is probably the better option. Replication is a lot more involved and will need a close eye to ensure thing are running smoothly.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply