Auditing the SQL Server is a major task for the DBA as well as for the developers. Developers and DBA should be regularly monitoring the changes done in the database where the key transactions have been made.
SQL Server provides various types of Audit
Database Level
To implement the Audit at the database level, the system provides a function of SQL Server Audit. This helps auditing an instance of the SQL Server Database Engine or an individual database involves tracking and logging events that occur on the Database Engine
Table Level
To Implement the audit at the Table Data level, there are two major mechanism
a. Change Data Capture
b. Change Tracking
The tracking mechanism in change data capture involves an asynchronous capture of changes from the transaction log so that changes are available after the DML operation. In change tracking, the tracking mechanism involves synchronous tracking of changes in line with DML operations so that change information is available immediately. The major difference is change tracking doesn't hold the history of the data.
For more details click here
SQL Server provides various types of Audit
Database Level
To implement the Audit at the database level, the system provides a function of SQL Server Audit. This helps auditing an instance of the SQL Server Database Engine or an individual database involves tracking and logging events that occur on the Database Engine
Table Level
To Implement the audit at the Table Data level, there are two major mechanism
a. Change Data Capture
b. Change Tracking
The tracking mechanism in change data capture involves an asynchronous capture of changes from the transaction log so that changes are available after the DML operation. In change tracking, the tracking mechanism involves synchronous tracking of changes in line with DML operations so that change information is available immediately. The major difference is change tracking doesn't hold the history of the data.
For more details click here