Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > User scenario: Recommended SQL server disk configuration

User scenario: Recommended SQL server disk configuration

Table of contents

Updated October 3, 2018


As of NTA 4.4, flow data is stored in its own SQL database. This database may be co-located in the same SQL instance as your Orion database, provided that the SQL instance meets the minimum version requirements for both modules. Both Standard and Enterprise SQL editions are supported.

This article provides an example configuration that can be used as guidelines when deploying NTA and other Orion Platform products utilizing a SQL database for data storage onto one SQL server instance.

For recommendations on sizing, see What are the hardware recommendations for the NTA 4.4 SQL Flow Storage database and the Orion multi-module system guidelines.


  • NTA 4.4


The following scenario assumes you are deploying NPM, NTA, and Log Manager onto one SQL server instance.

The load was distributed among the Main Polling Engine and 1 Additional Polling Engine as follows:

  • NPM: 24k elements
  • NTA: 50k flows per second
  • Log Manager: 1k syslogs per second sent to Main Polling Engine

The following hardware is recommended when deploying NPM, NTA, and LM onto one SQL server instance:

SQL server version

SQL Server 2016 SP1 or later

Standard or Enterprise edition

CPU 12-core Intel Xeon E5-4640V4 processor, 2.1 GHz or equivalent
Memory 64 GB
Hard disk

500 GB SSD drives

The following should use separate physical disks to divide workload types and avoid bottlenecks:

  • SQL Application installation
  • SQL data
  • SQL logs
  • OS PageFiles

For more information on separating physical disks, see Optimizing tempdb Performance (© 2018 Microsoft, available at, obtained on October 1, 2018)

This is a single tested configuration. Your results may vary.



Last modified