SolarWinds NTA Flow Storage database deployment options
As of NTA 4.4, the NTA Flow Storage database runs on a MS SQL server. You can either deploy the NTA Flow Storage database on one server with the Orion database, or deploy it on a dedicated server, depending on the size of your environment.
Use the native SQL management tools to monitor performance and resource utilization on your SQL server, and to tune your database server.
Orion database and the NTA Flow Storage database on one SQL server
You can install the NTA Flow Storage database and the Orion database on the same SQL server. For a complete overview of requirements, see the NTA 4.6 system requirements.
When evaluating SolarWinds NTA, MS SQL Server 2016 SP1 Express is installed by default. The Express edition of MS SQL server is not supported in a production environment, as it limits the database size and the performance of NTA. SolarWinds recommends changing the SQL server edition after the evaluation period.
Review the following requirements for installing the Orion database and NTA Flow Storage database on one SQL server:
- You must have a Standard or Enterprise edition of MS SQL Server 2016 SP1 or later for the NTA Flow Storage database.
- During configuration, you need to provide credentials to a compliant version of the SQL server used for the Flow Storage database.
When to install the NTA Flow Storage database on a separate server
You can install the NTA Flow Storage database and the Orion database on separate SQL servers. This option considers building a separate SQL server for the NTA Flow Storage database.
SolarWinds NTA 4.6 requires MS SQL Server 2016 SP 1 or later to run the NTA Flow Storage database.
The list below provides key resources to monitor and situations when you should consider a dedicated server for the NTA Flow Storage database:
- You are experiencing performance issues on the SQL server with co-located Orion database and NTA Flow Storage database.
- The NTA pages take a long time to load.
- Flow processing is slow. You see dropped packets in the logs, charts are empty or they have gaps, or you see less data than expected.
- Log files contain long running queries or SQL client timeout errors.
- The SQL server is heavily utilized.
- The performance of other Orion Platform modules is affected.