Page History
...
- Use previously configured audit settings as a baseline, or template, you deploy to multiple instances and databases so that the same events are audited across your environment
- Ensure all SQL Server databases used by regulated applications, such as SAP, are consistently audited and held to the same level of compliance
- Streamline and automate your configuration workflow
| Info |
|---|
If a user is assigned privileged status as part of the alert rule you are importing, and that user does not yet exist in the environment you are importing to, the privileged user status will apply if the user is ever added to your environment. |
| Info |
|---|
To execute a T-SQL script that applies previously exported audit settings, use the auditdatabase CLI command. |
Auditing the same events across multiple instances and databases
You can import previously configured audit settings to use as a baseline, or template. By deploying this baseline to multiple instances and databases, you can ensure the same events are audited across your environment.
To audit the same events across multiple instances or databases
...
- Navigate to Registered SQL Servers in the Administration tree.
- On the Registered SQL Servers tab, click Import.
- On the Select File to Import window, click Browse and locate the audit settings file, and then click Open.
- Click Next.
- If you want to audit events at the server level as well as events initiated by privileged users, select these import options.
- If you want to audit events at the database level, click Database Audit Settings, and then select the database you want to use as your baseline or template.
- On the Target Servers window, select the registered SQL Server instances to which you want to apply the selected audit settings, and then click Next.
- On the Import Audit Settings window, select the audit settings you want to import, and then click Next.
- On the Target Databases window, select the audited databases to which you want to apply the selected audit settings, and then click Next.
- On the Summary window, choose whether you want your imported audit settings to overwrite the settings on the target SQL Server instances and databases or be added to the settings already present. Click Finish to import your audit settings.
Auditing regulated applications across your environment
You can import previously-configured audit settings to ensure all SQL Server databases used by regulated applications, such as SAP, are consistently audited and are held to the same level of compliance.
To audit regulatory applications across your environment:
...
- Click Database Audit Settings, and then select the Only import for matching database names option.
- Select the databases whose audit settings you want to apply.
- If you also want to audit events at the server level as well as events initiated by privileged users, select these options, and then click Next.
...
follow the wizard steps below:
| Children Display |
|---|
...
...