Post reply

Transactional Replication for Archiving

  • April 28, 2011 at 11:44 am

    #99663

    We have a very simple archiving requirement on a very large database (1.5TB) and are trying to decide whether transactional replication is the correct solution. I know that transactional replication would at least get us in sync for the requirement that the archive hold all history and everything current up to 24 hours old. My question then becomes...if we then delete all data from production that is greater than 12 months, do those deletes get replicated and delete the data from the archive? If so then I think we will go a different direction and just do an SSIS package to move the data and delete from prod after commit.

    Owner & Principal SQL Server Consultant
    Im Your DBA, Inc.
    https://www.imyourdba.com/

  • May 2, 2011 at 4:04 pm

    #1318791

    In the article properties of the publication there is an option to 'do not delete replication'. Although I found in the past, you need to script out the publication and manually enter 'none' in the @del_cmd -

    example - @del_cmd = N'None'

    This will replicate all updates/inserts, but no deletes.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply