multiple NPM instances sharing the same database server

Hello Thwakers,

Is it possible to run multiple instances of Orion NPM using the same database server but with different instances?

I.e. 2 NPM VMs sharing the same database server (separate VM), but with different database instances (ex: SolarwindsOrion1 for NPM1 and SolarwindsOrion2 for NPM2).

What are the drawbacks other than performance issues?

Thank you in advance for your support.

Find more posts tagged with

multiple npm installations sharing same db server

npm

Accepted answers

pratikmehta003

as per the documentation, its not supported.

All comments

pratikmehta003

as per the documentation, its not supported.

dgsmith80

That's not technically correct.

The SolarWinds documentation says it doesn't support Multiple Orion server installations using the same database for obvious reasons. However, there is no restriction on using the same database server. I know plenty of people who don't have dedicated SQL Server just for SolarWinds they use the corporate SQL Server and host multiple instances.

If your DBA has the server setup correctly and the server specs are high enough then there shouldn't be a problem.

Regards

David

pratikmehta003

I would be interested to know if anyone has done it coz this can help in many scenarios... using a Shared DB for 1 Orion instance is fine but havent heard the same DB server having separate DB instance for separate Orion setups...

dgsmith80

It is possible, but I would suspect it isn’t’t common practice as not many people have a SQL Server with high enough performance to handle multiple instances of SolarWinds as it is a fairly intensive system.

i can prove it’s possible in our lab if you need proof for a business case example?

pratikmehta003

No David, thats fine.. :-)

zennifer

In VM Ware, you can do just about anything!!

I am getting ready to upgrade my Orion Platform, to include IPAM, NPM, SAM, NCM, VMAN, and NTA.

After a team discussion, we are going to set up a single Database server (VM Ware) that will server up:

Orion DB

GIS DB

Accounting DB

Environmental Systems DB

I am pretty sure that there are a couple more!

For Orion, I am splitting the Application (SAM) from the Network; they will have their own application servers.

The rest of the individual applications I listed will have their own app server, but will use the same database server - I am going to 2016 Server, 2014 SQL.

The answer to your question - yes, you can put multiple instance of Orion onto a single Database.

Your error above indicates that 2008 will not work with the latest releases of Orion, you need to upgrade to at least server 2012, and SQL 2010, but I would not do it on a Physical box.

ned1

I know that you can run many different instances on the same Microsoft SQL server (up to 50 instances). My question was if solarwinds support the same SQL VM for different NPM installations.

I guess it will work (I didn't test it), but if it is not supported by Solarwinds and later any issue goes on, Support team might tell you that your installation is not supported and you are left without technical support.

Thank you very much for the info zennifer

HerrDoktor

I'd also say that it is technically possible to host multiple solarwinds databases (each in a separate instance when using the default Name or specifying a separate name for each individual DB) on the same physical/virtual SQL Server.

like dgsmith80 said, the solarwinds documentation clearly states "using the same database"

However I would not recommend it unless you have a really really beefy SQL box.

I have 3 testsystems on the same instance each using a different database name.

ned1

Hi HerrDoktor

I do agree that this is technically possible, but will you still get support from solarwinds?

HerrDoktor

when you have a "performance issues case", they will find that bone and say it is related to SQL server performance.

To my knowledge it is a supported configuration as it is only stating "the same database". I never had any troubles with a support case.

grantallenby

I've done it on the same server. Just create a new DB instance and point your second Solarwinds at it. Away you go

grantallenby

I can confirm that you do still get support. I have been running two DB's on the same server for over 6 months now and still got full support when I needed to change some DB tables.

dgsmith80

Hi Ned,

From everything posted so far and the people I have spoken with nobody has ever had an experience that would indicate SolarWinds would cease support in this scenario. I would say the only caveat as per the comments about be warned that if there is an issue that is deemed SQL Performance related the SolarWinds support team are going to push the ticket back to you to prove that your SQL Server is performing as it should be, they don't really get involved in SQL much as it's outside the remit of the software.

grantallenby

Plus it says the same Database. Well technically its will be on a different DB but using the same server

tigger2

I haven't done it with multiple NPM's, but I've have a setup today with NPM (+ SAM + NCM), UDT, and IPAM all using different databases (each with a different name) inside the same database instance. It works fine but doesn't address the "high throughput/usage" concerns people seem to have if you tried multiple NPM's. Just pointing out that it would seem to work as the above products all run atop the same "Orion platform" (I believe), and if you installed each NPM on a seperate server OS/VM and pointed each one to a seperatly named database, the software shouldn't care.

As for support, they don't go out of their way to check/lock down that you're using multiple DB's on the same DB server (probably be hard to do anyway) and they let you choose to create a "new" or use an existing DB during install of these products, so it seems reasonable they mean "you can't install a (running) NPM into Database instance "A" named "SolarWindsOrion" and connect a second (running) NPM to the exact same database in database instance "A".

I think the docs are a bit confusing because: FOr MS SQL, the database(s), and the database instance/server that they exist inside of are separate things. They are usually talked about as if they are the same though . The docs should probably go more in depth/clarity as to what is/is not supported.

zennifer

Good info dgsmith80

pratikmehta003

tigger2 i agree with you on the document part.. its confusing

But glad to hear that ppl have tried and its working without any issues..