Log Shipping and Triggers

  • 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.

  • This was removed by the editor as SPAM

  • Hi

    DId you post this before?? swear i have read it..

    Anyhow, server 2 (log shipped db) will always be in standby mode, this is read only and the triggers will never fire. When the logs are applied, users of server 2 must be kicked. Remember S2 is a mirror of S1 since the last successful trans log applied.

    Cheers

    Ck

    Chris Kempster

    http://www.chriskempster.com

    Author of "SQL Server 2k for the Oracle DBA"


    Chris Kempster
    www.chriskempster.com
    Author of "SQL Server Backup, Recovery & Troubleshooting"
    Author of "SQL Server 2k for the Oracle DBA"

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

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