Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

LEM: Connector profile setting for Windows Server 2012 and MSSQL 2012

Hi,

I am trying to create a connector profile for Windows Server 2012 and MSSQL 2012, below are my requirements:

SQL Version	Server OS
2012 R2	Windows Server 2012 R2 Standard
2012 R2	Windows Server 2012 Standard
2012 R2	Windows Server 2012 Standard
Oracle 12c	Windows Server 2012 R2 Standard

Can you please advise me on correct settings.

I would like to thank you in advance.

regards

Sam

Find more posts tagged with

lem connector profile

Accepted answers

All comments

curtisi

Hey Sam,

The biggest question here is "Will you be running the Solarwinds LEM MSSQL Auditor or not? If yes, where will it be running?" MSSQL Auditor runs a trace against the database, and can pull in security events from within SQL, but that comes at a cost to database performance (every write, query, etc is going to incur a write to the audit logs). If you decide it's worth it, will you run MSSQL Auditor on every box or on one central box and query all databases from there?

In my lab, I have three SQL servers, and this is the profile for all three of them. They're different Windows and SQL versions, but this setup works on all of them, and this should cover all your listed SQL servers.

2016-05-26 14_43_58-SolarWinds Log & Event Manager.png

I have one box that runs MSSQL Auditor, and on that box, I have the following connectors configured, and really the only important one (for this scenario) is the first one to read the MSSQL Auditor:

2016-05-26 14_46_40-SolarWinds Log & Event Manager.png

Now, your Oracle box is going to be in it's own profile. The SQL stuff won't work for Oracle, but I have an Oracle server and my connectors look like this:

Again, only the top one is specific to Oracle.