Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > LEM: MSSQLAuditor Advanced Configuration

LEM: MSSQLAuditor Advanced Configuration

Table of contents

Updated 9/22/2017

Overview

LEM: MSSQLAuditor Advanced Configuration

 

Environment

  • LEM 5.4 or later

Detail

As of MSSQLAuditor version 5.4.0.0, there is an initialization file named MSSQLAuditor.ini that should be co-located with the MSSQLAuditor.exe executable file.

6.2.1 + you will need to create the ini file.  

 

The MSSQLAuditor.ini file may contain up to four individual settings that determine:

  • How large each log file may grow before rolling over to a new log file.
  • How many log files should be retained in the logs directory.
  • When to check log file size and total number of log files.
  • How long to wait before re-establishing connection to the SQL Server database.

 

The example below is what the default MSSQLAuditor.ini file that ships with the current MSSQLAuditor distribution looks like:

MSSQLAuditor.ini

; Optional ini file for MSSQLAuditor

; There are four values that may be tuned with this file

; Note that each entry starts in column one and there are no spaces or comments on the line

; If you wish to remove one of these and use the built-in program default, put a semi-colon (;)

; in front of the entry

;

[General]

; Maximum size of a log file. Default is 50000000 (50MB)

MaxLogFileSize=50000000

; Maximum number of log files allowed. Default is 10

MaxNumLogFiles=10

; Number of log lines to write before we check for the file size. Default is 100

CheckAfterLines=100

; Millisecond delay for attempting to reconnect to the SQL server. Default is 20000 (20 seconds)

DelayBeforeNewConnect=20000

 

Any line that starts with a semicolon is considered a comment line and ignored.

 

The settings and their use are explained in detail below:

 

MaxLogFileSize

This setting determines how large (in bytes) each log file should be allowed to grow before it is closed and another log file is opened to continue additional logging of data.

 

MaxNumLogFiles

This setting determines how many log files should be retained in the log file directory. When this size is exceeded, then the oldest file in the directory is deleted from disk.

 

CheckAfterLines

This setting determines how many log lines should be written to the log file before the number of log files is analyzed to determine if the oldest log file should be deleted or if the number of bytes being written to the log line will reach or surpass the maximum log file size so that a new log file can be created.

 

DelayBeforeNewConnect

This setting is the number of milliseconds to delay before attempting a new thread connection back to the SQL Server database. This value must be set higher than 999. If this value is less than 1,000, then it will default to 20,000 for a total wait of 20 seconds before attempting to reconnect to the SQL Server database.

 

MSSQL SQL Auditor Log Rotation

MSSQL Auditor is configured by default to store ten 50MB log files. A new file is created when the size reaches 50MB (approximately 100 lines). When ten log files are reached, the first file is recycled and a new log is started. 

 

 

 

Last modified

Tags

Classifications

Public