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
Store

>100 SQL Server connections

Hello,

I found out that NPM 8.5.1 SP3 opens lots of connections to the Orion DB on a remote SQL2005 Server.
When starting Orion there were about 170 connections open. 150 were caused by the alerting engine.

Is that a normal behaviour?

Oliver

Find more posts tagged with

database_connections

Accepted answers

FormerMember

Yes. That's normal.

All comments

FormerMember

Following theses posts I decided to check to see how many connections I was seeing on our Orion servers.

Orion 8.5.1 SP3 - 168

Orion 9.1 SP3 - 119

The SQL comamnd I used was:

select getdate() as Date,db_name(dbid) as 'Database Name', dbid,
Count(dbid) as 'Total Connections'
from sys.sysprocesses with (noLock)
where db_name(dbid) = 'NetPerfmon'
group by dbid

FormerMember

Yes. That's normal.

otatzmann

thx :-)

PatrickMorel

The User Login Rate alarm becomes active when the number of logins per second exceeds a threshold. This can be an indicator of poor application design. Creating a connection to SQL Server is relatively expensive, and coding practices where an application repeatedly connects and disconnects from SQL Server should be avoided.

While reconnecting will not necessarily slow down all users of the SQL Server, it will often result in poor performance for the application that is re-connecting all the time.

Spotlight Quest result.

Network_Guru

This sounds like the advanced alerting engine connecting at the interval specified for each alert.
I suspect if you have 10 alerts configured with checking every minute, then you would get 10 connects and disconnects per minute.
Perhaps not the best application design for Orion users with 100's of alerts setup?

<edit> can SW confirm this?</edit>

borgan

This thread is very interesting and brings to mind a question regarding good alert design.

Specifically, as the number of advanced alerts grows on your Orion system, what do you think are some good practices regarding advanced alert design with respect to the setting for Alert Evaluation frequency?

I'm hearing here that if you have 100 alerts with the frequency set at 1 minute, then you will likely have a problem.

So, what are the approaches that the user community uses?

otatzmann

That could be a reason, we have 15 Basic alerts and 24 advanced Alerts configured at the moment (I didn't check the interval for all of them yet)