Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Log & Event Manager (LEM) > Configure MSSQL Auditor to log SELECT statements in SQL Server

Configure MSSQL Auditor to log SELECT statements in SQL Server

Table of contents

Updated 8/24/2016

Overview

By default, MSSQL Auditor does not log SELECT statements from your monitored SQL Server. This article details how to modify the Auditor's trace definition file to accomplish that.

Environment

  • All LEM versions
  • MSSQL Auditor and SQL Profiler installed on a server
  • All SQL Server versions

Steps

  1. Open SQL Profiler on the server that is running the MSSQL Auditor.
  2. Select File > Templates > Import Template. Browse to C:\Program Files (x86)\SolarWinds Log and Event Manager MSSQL Auditor\tdfs and open the trace definition file that corresponds to your version of SQL Server.
  3. Select File > Templates > Edit Template and go to the Event Selection tab.
  4. Select the Show all events checkbox.
  5. Scroll down the list, select the checkbox for TSQL > BatchStarted, and click the Save button.
  6. Go to File > Templates > Export Template and overwrite the existing trace definition file. (You may wish to simply rename the old file and save this new file with the same name as the old file.)
  7. Restart the MSSQL Auditor service.

 

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 

Last modified

Tags

Classifications

Public