Page History
...
The Repository consists of the following databases. For more information, see How auditing works.
Repository Database Name | Description |
---|---|
SQLcompliance | Stores alert messages, audit settings, SQLcompliance Agent events, Activity Report Card statistics, and other SQL Compliance Manager configurations. |
SQLcompliance.Processing | Stores processing event data received from the SQLcompliance Agent. |
SQLcompliance.Instance | Stores processed events collected from a registered instance. |
SQLcompliance.Instance_Time_Partition | Stores archived events collected from a registered instance. |
Collection Server
The Collection Server processes trace files received from the SQLcompliance Agent, stores audit data in the events and archive databases, and sends audit setting updates to the SQLcompliance Agent. The Collection Server runs under the Collection Service account. By default, the Collection Server communicates with the Repository every five minutes (heartbeat) to write processed audit data to the event databases associated with the registered SQL Server instances.
...
The command line interface (CLI) provides an interface for third-party tools so you can automate and schedule regular tasks, such as audit data archival and grooming, and perform diagnostic tasks. You can also perform integrity checks through the CLI.
The CLI supports the following operations.
CLI Operations | Description |
---|---|
agentsettings | Lists the settings for the SQLcompliance Agent running on a specific SQL Server instance. |
archive | Archives audited events collected for registered SQL Server instances. |
auditdatabase | Enables auditing on a new database, allowing to specify either a regulation guideline or a custom audit template. |
checkintegrity | Verifies the integrity of audited events collected for a specific registered SQL Server instance. |
collect | Collects trace data from the agent. |
groom | Deletes audited events older than a specified age. |
help | Displays the CLI Help. |
listtriggers | Lists the CLR triggers for DML auditing on a specific registered SQL Server instance. |
registerinstance | Registers a new SQL Server instance and applies audit settings. |
removetriggers | Removes the CLR triggers from the subscriber table on the specific SQL Server instance. |
serversettings | Lists the settings for the Collection Server. |
timezones | Displays the time zones recognized by the computer hosting the Collection Server. |
updateindex | Applies optimized Repository index configurations to existing events and archive databases. |
Trace files and the trace directory
Trace files contain audited SQL Server events collected by the SQLcompliance Agent. The SQLcompliance Agent stores these temporary files in a secure directory on the audited SQL Server instance. When the set directory size threshold is reached, the SQLcompliance Agent stops the SQL trace until the trace files are sent to the Collection Server for processing. When the set file size threshold is met, the trace file is cycled. You can configure the SQLcompliance Agent trace file directory location as well as how the SQLcompliance Agent manages these files, such as how often the agent sends trace files to the Collection Server. For more information, see How the SQLcompliance Agent works.
Excerpt |
---|
SQL Compliance Manager audits all activity on your server. Learn more > > |
...
| Products | Buy | Support | Community | About Us | Resources | Legal