Installing audit tables on another database (4293253)

Applies to
ApexSQL Trigger

Summary
This article explains how to place ApexSQL Trigger auditing tables in a different database from the one being audited

Description
For this example, the database being audited is called "ApexSQLTriggerAuditedDB" The database where we want to store the audit information is called "ApexSQLTriggerStorageDB"

1. Start ApexSQL Trigger and create a new project. Connect to the "ApexSQLTriggerStorageDB"

   

2. From the Advanced tab, in the Architecture section, click the Install option. In the Install the Auditing architecture dialog check the following:
• Internal DDL
• Reports (Standard and/or Aggregate and/or DDL)

• Deleting the architecture

  

3. Click Run, and then Yes when asked if you want to run the installation script
4. Save the project
5. Create another project (or open the existing one). Connect to "ApexSQLTriggerAuditedDB"

   

6. From the Advanced tab, in the Architecture section, click the Install option.
   In the Install the auditing architecture dialog check the following:
• DDL

• Deleting the architecture



7. Again, click Run and then Yes when asked if you want to run the installation script

8. On the Home tab in the Triggers group, click the Edit template option:

   

9. In the template editor press Ctrl+F and in the search dialog search for

       DatabaseName = "[" & "ApexSQLTriggerStorageDB" & "]"

   

10. Change the DatabaseName variable to

        DatabaseName = "[" & "ApexSQLTriggerStorageDB" & "]"

    

11. Save the project
12. Make sure that users have updated rights to ApexSQLTriggerStorageDB
    When triggers are fired, the rights of the owners of the tables where the triggers are will be used
13. Recreate the triggers
14. To view audit reports, connect to the ApexSQLTriggerStorageDB

About ApexSQL Trigger
ApexSQL Trigger is a database auditing tool for SQL Server which allows you to monitor when and how the data was changed and who made the change. Audit SQL Server 2005 - 2014 databases