The Trace Options tab of the SQL Compliance Manager Agent Properties window allows you to configure how the SQL Compliance Manager Agent manages the trace files that contain collected events for auditing. Under the Trace Compression options, you can configure whether the Agent transfers trace files in a compressed format or without compression.
If you are modifying the properties for a SQL Compliance Manager Agent that is auditing a virtual SQL Server , SQL Compliance Manager will apply your changes to the active node in the cluster hosting the virtual SQL Server. SQL Compliance Manager Agent properties are later replicated from the active node to the passive node(s).
Available fields
SQL Compliance Manager Agent Trace Directory
Provides the directory path under which the SQL Compliance Manager Agent stores trace files.
Trace Collection Options
Allows you to specify the following settings:
- The rollover size (MB) at which the SQL Compliance Manager Agent should send the current trace file to the Collection Server, and create a new trace file to continue collecting events.
- Time interval (minutes) at which the SQL Compliance Manager Agent should send full trace files to the Collection Server.
- Maximum time (minutes) that should elapse before the SQL Compliance Manager Agent sends existing trace files to the Collection Server (if no trace files are received during the normal collection interval).
- Maximum time (seconds) that should elapse before the SQL Compliance Manager Agent's attempt to stop or start a trace file times out and returns a failure. By default, the timeout value is 30 seconds. Ensure this setting does not exceed the specified collection interval.
Trace Compression Options
Allows you to specify whether to send trace files to the Collection Server in compressed or uncompressed mode. By default the compression option is set to Compress.
Compress CM event files - trace files are compressed by the Agent and later decompressed by the Collection Server.
Do not compress CM event files - trace files are not compressed by Agent and therefore are not decompressed by the Collection Server, resulting in a performance enhancement.
Idera recommends CM users to consider excluding the Trace Files folder, on the agent and collection server side, from scanning of the MS or other 3rd party anti virus software, in order to reduce impact on resource utilization required for performing the scans.
The Trace Compression options are only available for SQL CM Agents in version 5.8. In case of older agent versions, this operation is not available. User will not be able to switch it to uncompressed transfer mode.
Trace Tamper Detection Options
Allows you to specify the amount of time (seconds) that should pass before the SQL Compliance Manager Agent automatically restarts the SQL trace. The SQL Compliance Manager Agent detects whether the trace is stopped, modified, paused, or deleted by another application. After the specified tamper detection interval, the SQL Compliance Manager Agent restarts the trace and records the trace status to the application event log.
Trace Directory Size Limit
Allows you to specify the maximum size threshold (GB) for the directory where you are storing the trace files. The directory size is checked at each heartbeat. To effectively manage the directory size, ensure you allow ample room to accommodate your auditing needs and set the SQL Compliance Manager Agent heartbeat interval at a low frequency.
Unattended Auditing Time Limit
Allows you to specify the maximum time threshold (days) for allowing the SQL Compliance Manager Agent to run without receiving a heartbeat.