At this step, you need to specify a database where Netwrix Auditor will store data collected from the data sources included in this monitoring plan.
NOTE: It is strongly recommended to target each monitoring plan at a separate database.
Configure the following:
|Disable security intelligence ...||
Only select this option if you do not want your data to be stored in the database. In this case, you will only be able to receive activity summaries. Reporting and alerting capabilities will not be provided.
To store data to the database, leave this check box cleared.
Default database name is Netwrix_Auditor_<monitoring_plan_name>.
It is recommended that you enter a meaningful name for the database here. It may include the data source type (e.g. Exchange_Audit_Data or OracleSrv02_Audit_Data), or so.
If you decided to use the existing SQL Server instance instead of dedicated, you may want to use Netwrix_Auditor prefix to distinguish Netwrix Auditor databases from others.
|Use default SQL Server settings||Select this option if you want Netwrix Auditor to connect to the SQL Server instance using the default settings you specified Default SQL Server Instance .|
|Specify custom connection parameters||
Select this option to use custom credentials when connecting to SQL Server. Specify authentication method and the account that Netwrix Auditor will use.
Make sure this account has sufficient rights to connect to SQL Server and work with the databases. See Configure Audit Database Account for details.
Netwrix Auditor will connect to the default SQL Server instance and create a database with the specified name on it.
NOTE: Global settings that apply to all databases with audit data (including retention period and SSRS server used for reporting) are available on the Audit Database page of Netwrix Auditor settings. See Audit Database for details.