Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Netflow Traffic Analyzer (NTA) > Troubleshoot local NTA Flow Storage Database

Troubleshoot local NTA Flow Storage Database

Table of contents

Issue

If you are installing NTA Flow Storage Database on the same server as your NPM/NTA and Orion SQL Database, you can experience performance problems.
This configuration is not recommended because all performance extensive components (NTA/NPM, Orion SQL Database, and NTA Flow Storage Database) share the same hardware. If you still need to use this configuration, you can try to optimize NTA using the following workarounds. However, to achieve optimal performance, consider installing NTA/NPM, Orion SQL Database and NTA Flow Storage Database on separate servers.

Resolution

Try one of the following workarounds:
  • Install the NTA Flow Storage Database on a different physical disk that the SQL database.
  • Limit the memory allocated for SQL. For more information, see this Microsoft Support article.
  • Limit the number of processors that can be used by SQL.
Last modified

Tags

Classifications

Public