Home Forums SQL Server 2014 Administration - SQL Server 2014 Adding multiple triggers to same table - Recommendations/Best Practices RE: Adding multiple triggers to same table - Recommendations/Best Practices

  • February 20, 2018 at 10:12 am

    #1980492

    RonKyle - Tuesday, February 20, 2018 8:32 AM

    Still does not answer the question. What is the justification for essentially copying 500 tables to a second location?

    We have found a replicated version necessary for intra day downloads.  The data warehouse extract has sufficient pull on the database as to interfere with the users if pulled during the day from the primary server.  Pulling from a replicated version, which is a complete copy, is a significant advantage.  It also acts as a go to database in the event of an issue with the primary database.

    Valid explanation.  I'm actually trying to find out why the OP determined that a similar, and vastly more complicated, approach was required for their environment.

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/