Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Indicates whether SQL Compliance Manager has encountered any issues while auditing your SQL Server environment.

Clicking the status link opens the more detailed Registered SQL Servers tab under Administration. Use this tab to see view the status of audited databases on this instance, validate audit settings, and check the SQLcompliance Agent status.
 

Status TypePossible Causes
Alert/Error
  • The Repository is installed on a SQL Server 2000 instance but a SQLcompliance Agent has been is deployed to a SQL Server 2005 or later instance. For example, to audit activity on instances running SQL Server 2005, install a second Repository on a SQL Server 2005 instance.
  • A version 1.1 SQLcompliance Agent has been is deployed to a SQL Server 2005 or later instance. Version 1.1 does not support auditing SQL Server 2005 instances. To continuing auditing SQL Server 2005 instances, upgrade the agents to the latest version.
  • The SQLcompliance Agent has missed every heartbeat over the last 24 hours. This issue occurs when the SQLcompliance Agent service is stopped, the Collection Server is offline, the computer hosting the agent is offline, or network availability is lost.
  • The SQLcompliance Agent service is no longer running. The SQLcompliance Agent service is stopped by a SQL Server login or a third-party application.
  • A system alert has been is triggered. System alerts notify you when the health of your SQL Compliance Manager deployment may be compromised. For more information, see the Activity Log tab.
OKSQL Compliance Manager is performing as expected.
Warning
  • No SQL Server instances have been are registered with SQL Compliance Manager. SQL CM cannot begin auditing your environment until instances are registered, SQLcompliance Agents are deployed, and audit settings are configured.
  • The SQLcompliance Agent has is not yet been deployed to an instance that is registered with SQL Compliance Manager. SQL CM cannot audit this instance until an agent is deployed and audit settings are configured.
  • A deployed SQLcompliance Agent has not yet contacted SQL Compliance Manager. This issue occurs when the SQLcompliance Agent service is stopped, the computer hosting the agent is offline, or network availability is lost.
  • A deployed SQLcompliance Agent has missed two sequential heart beats. This issue occurs when the SQLcompliance Agent service is stopped, the computer hosting the agent is offline, or network availability is lost.

...

Displays the number of instances currently being audited. This number does not include instances where auditing is not yet configured or is disabled.

...

Displays the number of databases currently being audited. These databases are hosted by SQL Server instances that are registered with SQL CM. This number does not include databases where auditing is not yet configured or is disabled.

...

Displays the number of audit events stored in the Repository event databases for the selected time span. This number does not include events that were previously archived or groomed events.

Understanding the Enterprise Activity Report Card status

Each tab of the Enterprise Activity Report Card provides an auditing status for the corresponding event category. You can use Use this status to help you determine whether you are effectively auditing events in your environment.
You can also use auditing thresholds to display critical issues or warnings should a particular activity, such as privileged user events, be higher than expected. These thresholds can notify you about issues related to increased activity levels, such as a security breach, that may be occurring on this instance. Use thresholds to supplement the alert rules you have configured for your environment.

Status TypeIndicationMeaning
Audited without thresholdsgray checkThis event category is being audited on instances in your environment, but auditing thresholds are not set for this event category.
Consider setting audit thresholds so you can track peaks in activity and identify any suspicious events.
Criticalred iconThe event activity during the selected time span is higher than the defined critical threshold.
To see more information about this activity, navigate to the Audit Events tab and search for events in the flagged event category that is flagged. You can view the detailed properties of an event by double-clicking the listed event.
OKgreen checkThis event category is being audited on instances in your environment and auditing thresholds are set for this event category.
Not auditedred iconThis event category is not being audited on instances in your environment even though auditing thresholds are set for this event category.
To track this activity, change your audit settings to include the corresponding event category.
To ignore this activity, disable the auditing threshold set for this event category.
Not audited and no thresholds setgray circleThis event category is not being audited on any instances in your environment. Auditing thresholds are not set for this event category.
Review whether you need to audit and track this activity on any of your SQL Server instance.
Warningyellow iconThe event activity during the selected time span is higher than the defined warning threshold.
To see more information about this activity, navigate to the Audit Events tab and search for events in the event category that is flagged. You can view the detailed properties of an event by double-clicking the listed event.

...

For more information about specific alerts, see the Alerts tab. You can view which alerts have been are generated from multiple instances across your environment or from a particular instance.

...

Opens the Change Log tab under Administration, allowing you to monitor what types of changes have been are made to audit settings across your environment.

...