December 1, 2003 at 10:42 am
30GB database, many tables with millions of rows. S1 is transactional server, S2 is reporting server, S3 is archive server. S1 updates S2 via log shipping. S2 updates S3 via archive process where changes are applied to S3 and "old" data removed from S2.
If triggers are applied to the reporting server that is updated via log shipping, will the triggers still fire? Plan is to implement triggers on tables on reporting database to store the PK of the rows updated to shorten archive process. I can't find anything on this any where.
December 1, 2003 at 1:21 pm
I'm afraid your strategy won't work. The receiving logshipped database must remain in "loading" or "standby" state. Any changes will break the log shipping chain.
Archiving will need to be from S1 to S3.
Cheers,
- Mark
Cheers,
- Mark
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply