Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > MSSQL Auditor configuration options

MSSQL Auditor configuration options

Table of contents

Updated July 3, 2017


This article describes the changes and customization that can be made to SolarWinds MSSQL Auditor. 


LEM 5.4 and later


The MSSQLAuditor.ini initialization file in MSSQL Auditor is co-located with the MSSQLAuditor.exe executable file and 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 the log file size and the total number of log files
  • The wait time before re-establishing connection to the SQL Server database

The following is an example of the initialization file:


; 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



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


; Maximum number of log files allowed. Default is 10


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


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



This is also what the default MSSQLAuditor.ini file shipped with the current MSSQL Auditor distribution looks like.

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


The following are the actual settings and their detailed use:

  • 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 the 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 delay value in milliseconds 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 time 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