Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Archive > 2018May01 - Deletes > 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

This page has no custom tags.

Classifications

Public