Audited events in ApexSQL Audit

This article provides a list of SQL Server events for each operation type group used in ApexSQL Audit GUI (DDL, DML, Query, Execute, Error, Warning, and Security).

The events audited by ApexSQL Audit are divided into 7 groups, by operation type.

ApexSQL Audit custom queries and reports

ApexSQL Audit provides a range of built-in queries as part of the reporting module that cover the most common user reporting requirements. For more specific reporting requirements, we have provided a possibility to create custom SQL Server auditing reports by using a drag-and-drop technique. If this still doesn’t provide the specific information you need, you will still be able create queries and reports of your own using T-SQL , due to the fact that ApexSQL Audit stores all audited data in a SQL Server database.

ApexSQL Audit Tamper-evident design features

ApexSQL Audit stores all configuration and audited data, from local and remote SQL Server instances in a centralized repository database named ApexSQLCrd. The packages with captured data are transferred automatically and safely via network, parsed, and data is stored into the central repository database. This approach makes it is easier to backup and protect captured data.

ApexSQL Audit Central Repository Database design

All configuration and audited records from all audited SQL Server instances are stored in a centralized auditing repository database called ApexSQLCrd. The tables in the ApexSQLCrd database are

ApexSQL Audit limitations

This article describes the limitations you should consider when working with ApexSQL Audit.

The maximum number of audited distributed instances
There is no specific limit on the number of auditing instances (remote SQL Servers) that may be audited. The maximum number depends on your environment, the number of transactions executed against audited servers/databases and network bandwidth. The more distributed instances, the more likely it may be for you to encounter performance problems, as a large number of packages transferred through your network can cause bottlenecks.

When to use ApexSQL Restore

ApexSQL Restore can attach native or natively compressed backups and backup sets created in SQL Server 2000 and above to any edition of SQL Server 2005 and above, including full and differential database backups as well as transaction log backups

As such, ApexSQL Restore is very useful, among others, in the following scenarios:

How to use ApexSQL Script to deploy a database as a .Net executable

See how to script both structure and data for a database, and how to compile it into a .Net executable

The good news about the executable is that it can be executed even on the workstations without the SQL Server client tools installed

  1. Run ApexSQL Script
  2. Connect to a SQL Server instance
  3. Select a database and click Load

  4. Select the objects to script on the Structure tab

  5. On the Data tab, select the tables in views of which you want to script the data

  6. On the Home tab, in the Actions group, click Script wizard
  7. Select Structure and data in the Scripting mode page:
  8. Select Executable installer in the Output type page:

  9. Click Next
  10. Select the Include dependent database objects option to avoid constraint problems

  11. Click Next
  12. Select the options for the executable file

    1. Check Run executable now to execute the created exe file immediately after it’s been created
    2. Specify the database name, MDF and LDF file directories, collation, recovery model, and size

  13. Click Create

  14. Specify the file name and the patch for the created file. The executable file is started as soon as it’s created

  15. Select Create new database, specify the database name to create a new database, and run the file against it
  16. To specify what to do when an error is encountered, click Options and in the Error handling section choose between Abort, Ignore and Ask for confirmation options:

  17. Specify the database MDF and LDF file directories, collation, recovery model, and size on the Database properties pane:

Last updated

August 21, 2018