The Registered SQL Servers tab lists the SQL Server instances that are registered for IDERA SQL Compliance Manager to audit. This list includes the following types of registered servers:
- SQL Server instances running in trusted domains
- SQL Server instances running in non-trusted domains or workgroups
- Virtual SQL Servers hosted by Microsoft failover clusters (Microsoft Cluster Services)
Registering a SQL Server instance allows you to audit events at the server and database levels. You can configure audit settings for each registered instance and hosted database.
This tab lists the registered SQL Server instances you have audited. Auditing allows you to collect specific events from the SQL Server trace. This list contains SQL Servers you are currently auditing. If you disabled auditing on a SQL Server instance , this window continues to list the server until you remove the server.
Available actions
Register New Server
Allows you to register an additional SQL Server instance with SQL Compliance Manager.
Register New Database
Allows you to enable auditing and configure audit settings for a database on the selected SQL Server instance. To manage settings for a database you are currently auditing, use the Audited Database Properties window.
Enable Auditing
Allows you to enable auditing on the selected SQL Server instance. When you enable auditing, the SQLcompliance Agent begins collecting events on the selected SQL Server instance, and sends the SQL trace files to the Collection Server.
Disable Auditing
Allows you to disable auditing on the selected SQL Server instance. When you disable auditing, the SQLcompliance Agent stops collecting new event data, and stops the corresponding SQL trace. You can continue to view and report on previously audited events or archived events.
Server Settings for Audited Server Activities
Allows you to view and modify audit settings for the selected SQL Server instance.
Server Settings for Privileged Users
Allows you to view and modify which privileged users are audited on the selected SQL Server instance.
Database Settings for Audited Database Activities
Allows you to view and modify audit settings for the selected database. This action is available when you select a database from the Audited Databases list.
Database Settings for Trusted Users
Allows you to view and modify which users are considered trusted users on the selected database. Trusted users are not audited.
Import
Allows you to import audit settings previously exported from another SQL Server instance or database.
Export
Allows you to export audit settings configured for this SQL Server instance to an XML file. You can later use this file to import audit settings across multiple SQL Server instances or databases, ensuring consistent alerting on activity throughout your environment.
Update Now
Allows you to send your audit setting changes to the SQLcompliance agent immediately. Typically, the Collection Server sends audit setting updates at each heartbeat communication from the SQLcompliance Agent. By default, a heartbeat occurs every five minutes. To view the SQLcompliance Agent heartbeat details, use the General tab on the SQLcompliance Agent Properties window.
Collect Audit Data Now
Allows you to force the SQLcompliance Agent to send trace files to the Collection Server for processing. Typically, the SQLcompliance Agent sends trace files to the Collection Server at the specified collection interval. By default, a trace file collection occurs every two minutes.
Agent Properties
Allows you to view and modify settings for the SQLcompliance Agent that is auditing the selected SQL Server instance.
Check Agent Status
Allows you to check the status of the SQLcompliance Agent on the selected SQL Server instance, such as whether or not the agent is active.
Deploy Agent
Allows you to deploy the SQLcompliance Agent to one or more registered SQL Server instances. Deploying the agent installs the SQLcompliance Agent Service on the target instance, and allows you to begin auditing events.
Upgrade Agent
Allows you to upgrade the SQLcompliance Agent on the selected SQL Server instance to the current version. This option is available if the agent was remotely deployed through the Management Console. To upgrade an agent that was manually deployed, run setup.exe from the SQL compliance manager installation kit on the target SQL Server computer.
Change Agent Trace Directory
Allows you to specify a different trace directory for the SQLcompliance Agent. The agent uses the specified folder to store trace files before sending these files to the Collection Server for processing.
Refresh
Allows you to update the Registered SQL Servers list with current information.
Remove
Allows you to unregister the selected SQL Server instance. When you remove a SQL Server instance, SQL Compliance Manager disables all auditing at the server and database levels on the SQL Server instance. If the selected instance is the last instance to be audited on this SQL Server , SQL Compliance Manager also uninstalls the SQLcompliance Agent. If you manually deployed the SQLcompliance Agent , you must manually uninstall it from the SQL Server computer.
Available columns
SQL Server
Provides the name of the SQL Server instance, using the format SQLServerName\InstanceName.
Status
Indicates whether SQL Compliance Manager detected an auditing or configuration issue. For example, if the selected SQL Server instance is unavailable, SQL Compliance Manager displays an error.
If a system alert is triggered , the Status column displays the alert type. System alerts notify you when the health of your SQL Compliance Manager deployment may be compromised. For more information, see the Activity Log tab.
Audit Status
Indicates whether auditing is enabled on the selected SQL Server instance. When auditing is disabled, the SQL trace is stopped and the SQLcompliance Agent no longer collects events.
If a system alert is triggered , the Audit Status column instruct you to view the Activity Log to determine which event triggered this alert.
Last Agent Contact
Provides the date and time when the SQLcompliance Agent last received audit setting updates from the Collection Server (also called a heartbeat). To view the SQLcompliance Agent heartbeat details, use the General tab on the SQLcompliance Agent Properties window.