Date: Fri, 29 Mar 2024 00:31:30 +0000 (UTC) Message-ID: <306425877.69505.1711672290905@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69504_1500076209.1711672290900" ------=_Part_69504_1500076209.1711672290900 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You can receive alerts when IDERA SQL Compliance Manager detects= a specific event or operational status Alerting on event data collected fr= om your audited SQL Server instances and databases provides the information= you need to immediately correct issues that threaten your compliance with = federal and corporate security and privacy policies. Alerting on operationa= l status allows you proactively identify performance issues before your SQL= Compliance Manager deployment is impacted.
You can also generate reports on alert activity, allowing you to provide= forensic information and demonstrate policy enforcement. For more informat= ion, see Report on Audit = Data.
Use the following checklist to help you prepare your environment to succ= essfully use Event Alerts to analyze audit data collected from your SQL Ser= ver instances and databases.
:tick: | Follow these steps ... |
---|---|
:tick: | Ensure your Windows logon account has sysadmin p= rivileges on the SQL Server instances hosting the Collection Server. For mo= re information, see Hard= ware requirements. |
:tick: | Review how the alert process works and which SQL= events you can detect using alerts. For more information, see How Event Alerts work. |
:tick: | Identify the types of audit data you want to be = alerted on. Determine which events should generate alerts and the condition= s under which the alert should be generated. Also consider whether you want= an alert message written to the event log or emailed to a specific account= . For more information, see Use Event Alerts to analyze audit data. |
:tick: | For each type of audit data you want to alert on= , create an alert rule using the criteria you identified. For more informat= ion, see Create an = Event Alert rule. |
:tick: | If you want to receive alert notific= ations through your email account, test your email configurat= ion settings to ensure SQL Compliance Manager can access your SMTP server. = For more information, see Receive alerts through email. |
:tick: | Review how you can implement Reports in your SQL= Server environment. For more information, see Report on Audit Data. |
Use the following checklist to help you prepare your environment to succ= essfully use Status Alerts to identify performance or operational issues in= your SQL Compliance Manager deployment.
:tick: | Follow these steps ... |
---|---|
:tick: | Ensure your Windows logon account has sysadmin p= rivileges on the SQL Server instances hosting the Collection Server. For mo= re information, see Hard= ware requirements. |
:tick: | Review how the alert process works and which SQL= events you can detect using alerts. For more information, see How Status Alerts work. |
:tick: | Identify the product components whose status you want = to audit. |
:tick: | For each type of status data you want to alert o= n, create an alert rule using the criteria you identified. For more informa= tion, see Create a Statu= s Alert. |
:tick: | If you want to receive alert notific= ations through your email account, test your email configurat= ion settings to ensure SQL Compliance Manager can access your SMTP server. = For more information, see Receive alerts through email. |
:tick: | Review how you can implement Reports in your SQL= Server environment. For more information, see Report on Audit Data. |