To use Auditing and Reporting with the Server, you have to enable the Auditing and Reporting Module (ARM), specify the Host/Instance Name, Database Name, and login information, then specify the action to take in case of database error. The procedure below describes how to configure ARM.
In the Administrator, connect to the server, then click the Server tab.
In the left pane, click the Server you want to configure.
In the right pane, click the Server Options tab.
In the Database Audit Settings area, select the Enable Auditing and Reporting check box.
In the Host(\Instance Name) box, specify the Server name or IP address, or provide a DSN or DSN-less connection string.
Provide the Username and Password for connecting to the database. (You provided these when you installed the module.)
Provide the Database Name.
Optionally, click Test Connection to verify that you can connect to the database.
Select an action for the Server to take if there is an error with the database.
To stop recording data, select Stop auditing.
To continue recording data to a file, select Audit to folder, and specify the location of the file.
In the Failure notification e-mail address box, specify the e-mail address to which the Server is to send connection error notification. To provide more than one e-mail address, separate the addresses with a comma or semicolon. The Server uses its global SMTP e-mail settings for SMTP Configuration to send the e-mails, so make sure that those settings are correct.
Database error e-mails contain the following information:
The time the Server detected the database error
Error code - an indicator of any specific connection error or database engine transaction error codes
Error description - textual description provided by the database engine for the specific error
The database instance name and database name
Secure FTP Server IP address and/or DNS name
The location of the text file if text file logging was selected
Instructions for use of RECONNECT to reestablish database communications and instructions for insertion of the SQL transactions using osql
|
|
If you are using Windows 2000 for your server installation, you must update MDAC prior to install. You can find the latest update at: http://msdn.microsoft.com/data/ref/mdac/downloads/ This does not apply to Windows XP, Windows 2003, or later versions, because they come with a newer version of MDAC that is compliant. |
