Two Orion Installations connecting to the same Database?

Yes, just be sure to choose a new database in the config wizard and give it a unique name. Depending on how many elements you have you might bog down the SQL server. Check the SQL server health first.

http://www.solarwinds.com/documentation/Orion/docs/OrionPerformance.pdf

Andy

I wanted to be sure I understood your answer correctly.  I CAN connect a new instance of Orion on a new server to the existing SQL database WHILE the old Orion instance is running.  Is this correct?

SQL performance isn't an issue (the SQL team gets more funding than we do and the cluster is ridiculously powered)

pjcarter12,

We would not support having 2 NPM servers writing to the same database. You will have many many issues.

I think Andy was thinking you were creating a new database on the same database server. That would be fine. Using the same DB for 2 servers actively collecting would not.

Michael

Yes, what you will be doing is creating a new and uniquely named database on the same SQL server. We do this all the time. Just use a unique name (not the default name) for the new db.

I am not sure if it is what you want, but you could create clone of your actual database and new NPM installation could be run against cloned database. Of course original database and cloned database won't be related in any way.

This is what I've done in the past to test new versions RCs and betas without having to re-add a bunch of junk.  then I just delete a good bit of the environment if needed for load.

keep it on the same DATABASE SERVER but copy to different name like NetPerfMonBETA or something.

you can not have two implementations talking to the same database (like netperfmon) as it will have troubles with primary poller, who is polling what, data overwritten, etc..  general chaos.