SQL Cluster 2005 Issue

The Backend for our Orion NPM Poller is our SQL 2005 Cluster. Tuesday night I failed over the cluster SQL Cluster from one node to another. Everything seemed to be working fine in Orion. On Thursday morning I noticed that Orion stopped collecting Historical Data when the SQL cluster failed over. Has anybody else seen this behavior in Orion NPM v7.8? Everything else about Orion seemed to be working fine. I ran through the config wizard and had Orion reconnect to the database and then it started logging historical data again.

GB

Find more posts tagged with

sql_cluster

Accepted answers

All comments

FormerMember

We have this same problem with Orion NPM 9.1. It's a pain.

vhcato

Has anyone else run into this?

Does anyone from SW have any thoughts? We are seriously considering moving to a clustered SQL solution for our Orion instance, and this issue partially negates the reason for having the cluster in the first place.

tdanner

We haven't tested with clustered SQL and honestly don't have much experience with it. The database connection string is in SWNetPerfMon.db (one copy in \program files\solarwinds\orion for the services and another copy in \inetpub\solarwinds for the website). A DBA with cluster experience might be able to tweak that connection string to make it do the right thing.

juliandaniel

Orion is now becoming a critical service for us so moving on to a SQL cluster for the highest availability is now a must for us. Should this not be something Solarwinds looks into