Husky Audit

Husky Audit - a tool for software developers, which increases the speed of development through the use of a ready-made solution in the field of monitoring data changes made by users. The tool is designed for integration and use with end-products that use the Microsoft SQL Server database as a data warehouse. Purpose: to provide accurate information about the history of changing any portion of data in the main system. Husky Audit Objectives

1. Delimit insertion, modification and deletion events.
2. For any one that falls under predetermined criteria for inserting, deleting, or modifying data, store the fact of the event in the change log.
3. Have the ability to store authorization information about the user who made the data change.
4. Have the ability to take user's authorization information not only from the connection to the database, but also provided by other methods (application).
5. Have the ability to save the data that has changed as a result of the event.
6. When changing fields that are links to fields in other tables, also save key fields from such external tables that are relevant at the time of the event.
7. Have the ability to sample change log data in different sections and according to certain criteria.
8. Clean up obsolete and no longer needed log data, either on a schedule or manually.

The subsystem is implemented in the form of the following structural components:

1. Table of data changes events. This table records all the necessary parameters for each data modification event, one line per event.
2. The table of the changed data. The table itself records the modified data itself
3. Triggers on each table of the main system , Whose data is to be audited.
4. User interface for creating triggers on the main system tables. This interface after its launch on the basis of the database schema recreates all the triggers on the main tables, thus updating all the changes that could occur in the database schema during the evolution of the system. After any modification of the system tables, it is enough to start this procedure to update the audit mechanism.
5. A stored procedure for clearing out the old audit data.
6. Various specialized representations, Which can be created on the basis of the tables in items 1 and 2 in order to simplify the development of the main system in terms of processing audit data.