Hide this message
Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at firstname.lastname@example.org
This article gives an overview of the level of auditing provided by the LEM agent.
All LEM versions
The SQL Auditor uses the MSSQL Profiler with trace files that look for specific types of activity. In order to avoid having any visibility into credit card, patient, or other potentially personal information that might pull the LEM appliance under specific regulations (or put sensitive data in a database where it should not belong), it is generally avoided tracing any query activity that would log values being inputted, updated, and deleted.
It is capable to use Profiler/traces to audit anything done against a database, but MSSQL Auditor specifically looks for:
These could be made from either the query window, a remote tool, or any application that accesses the database.
SolarWinds have had customers request or provide additional trace auditing, but SolarWinds advised against capturing anything that might have actual query/insert data in it since that could be either stored in a log file (in plain text) on disk on the system and/or in the LEM database.
Note: MSSQL Auditor can be responsible for sending a huge amount of traffic to LEM so it is wise to consult Microsoft documentation on best SQL Auditing practices.