The Before-After Data window of the Apply Regulation Guidelines configuration wizard allows you to select the tables for which you want to collect before and after data. You can collect before and after data for DML events generated by DELETE, INSERT, and UPDATE commands.

Collect before and after data when it is critical to capture the exact data change in a table column. When this feature is enabled, you can evaluate the before value and after value for each change in the Audit Events view. Enabling this feature can impact your Collection Server and Management Console performance.

If you want to collect before and after data, verify that you are auditing DML events on this database and that common language runtime (CLR) is enabled on the corresponding SQL Server instance.

IDERA provides limited support for before-after data auditing of the publisher database in SQL Servers with replication. However, this scenario is supported only when the publisher database with transaction replication is set to replicate data ONLY. If the target database uses SQL Server replication set to replicate more than data, do not enable before-after auditing. Before and after data collection does not support SQL Server replication in that situation. For more information, see Microsoft Books Online for the version of SQL Server you are using.

To successfully audit specific columns on a table, ensure the table name does not contain the following special characters: \ / : * ? "

Available actions


Select a database from the list and click Configure to open the Configure Before After Data Change window where you can add, edit or remove your specific user tables for Before-After Data auditing.

IDERA | Products | Purchase | Support | Community | Resources | About Us | Legal
  • No labels