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

persistent connections

I just moved my Solarwinds DB to a new SQL Cluster (has always been on its own server) and my Database Admin is now seeing, due to more logging, that NPM is logging in and off nearly a billion times in just a few hours. It created 150GB of logon/logoff logs in just 2 hrs. My DB admin is asking if Solarwinds supports persistent connections or connection pooling?

Has anyone else noticed this before? I would believe this could slow down by SQL access times logging in and out for every poll.

Find more posts tagged with

Accepted answers

All comments

MarieB

afsprau--

A billion times? Yikes. If you don't get a resolution to this, contact support.

bshopp

How many elements do you have and what is your polling interval set to? Also do you have a lot of alerts defined and setup as well as Universal Device Pollers?

afsprau

Hello,

We do have allot of elements 25,732 mostly interfaces.

Default node and Interface polls = 120 Sec

Default Polling Statistics = 10 - 15 minutes

Maybe 35 - 40 Different Alerts

We also do use the Universal Device Poller but do not poll too many different things, maybe 12 different pollers on different devices.

bshopp

How many additional pollers do you have? 2-3?

afsprau

At this time we have the main poller and 1 additional poller, Looking at adding atleast one more soon as we upgrade from 9.5 to 10. I know the additional poller is greatly need at this time and should help speed dramatically, but still questioned if NPM logs on and off every time it dumps any poll information to the DB.