NTA SQL - Moving the SQL DB to a new Server

Is it very difficult to move the NTA SQL DB to a new server? Ever since the update to 4.4 I did back in June Solarwinds has been unreliable and we are thinking it might have to do with the NTA SQL upgrade. When NTA the database was on its own flat file server Solarwinds ran fine and since upgrading and putting on the same SQL DB server as the Solarwinds and DPA database I have had nothing but problems. Just seeing if anyone else has the NTA SQL on its own SQL server separate from the rest of the Solarwinds DBs. The SQL server is running SQL Server V17.1 SP 2, 8 CPUs, and 128GB of RAM. Thanks! - Dave

Find more posts tagged with

Accepted answers

All comments

gkjono

Typically, you will want the NTA Flow Storage Database on its own server in a production environment. It's not hard to move though. You'd stop all of your Orion services, backup the database, restore it on the new server, then rerun the configuration wizard on all of your polling engines and point it to the new server. This article walks through it.

Move the NTA Flow Storage database to a different SQL server - SolarWinds Worldwide, LLC. Help and Support

-Greg Kjono

Loop1 Systems: SolarWinds Training and Professional Services

LinkedIN: Loop1 Systems
Facebook: Loop1 Systems
Twitter: @Loop1Systems

martian_monster

So NTA was on its separate server until I did the 4.4 update that updated the NTA database to SQL. Right now all of my SQL DBs running Solarwinds are on a separate server from my SQL App server. My reason for wanting to move the NTA DB was to see if that is causing some of my problems in Solarwinds - the new NTA SQL DB on the same SQL server as my Solarwinds and DPA DB. I have moved Solarwinds DBs to new servers before this was just me wanting to troubleshoot some of my Solarwinds issues.

neomatrix1217

What type of issues are you having since moving it to SQL?