Database activity monitoring (DAM) : Configuring target database monitoring : Configuring Microsoft SQL Server monitoring
 
Configuring Microsoft SQL Server monitoring
FortiDB uses either SQL Trace or the TCP/IP sniffer to collect audit information from Microsoft SQL Server databases.
The TCP/IP sniffer is provided by the appliance version of FortiDB only. For detailed configuration instructions, see “Configuring monitoring using the TCP/IP sniffer (all database types)”.
To configure auditing for a Microsoft SQL Server database using SQL Trace
 
To change the collection method or polling frequency for monitoring, first stop monitoring. You cannot change these settings while FortiDB is monitoring the target database.
1. Ensure the required database pre-configuration is complete.See “Microsoft SQL Server target database pre-configuration”.
2. Verify that the SQL Server has an audit trace folder (for example, C:\SQLTrace).
Ensure that you enter the full path to the folder.
3. In the navigation menu, click DB Activity Monitoring > Monitoring Management, and then click the name of the target that connects to the database you want to monitor.
4. On the General tab, complete the following settings:
Collection Method
Select SQL Trace.
To change a collection method from one option to the other, first stop monitoring, change the collection method, then restart monitoring.
Trace Folder
Specify the folder where your server writes the trace information.
Ensure that you enter the full path.
Polling Frequency (ms)
Enter the polling frequency for audit collection, in seconds
To change the polling frequency later, stop monitoring, change the value, and then re-start monitoring.
5. Click Test to confirm the connection with the method you selected.
6. On the General tab, under Monitoring, click Start Monitoring.
For more information about monitoring, see “Monitoring settings and messages”.
See also
Target monitoring configuration tabs and options
Microsoft SQL Server target database pre-configuration