Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > Can I migrate my historical data from the SQL Flow Storage

Can I migrate my historical data from the SQL Flow Storage

Table of contents

Updated January 12, 2017

Overview

Can I migrate my historical data from the SQL Flow Storage?

 

Environment

  • NTA 4.2.3 and lower versions

Detail

Yes. During the Configuration Wizard, you can choose to migrate the historical data from SQL. The migration runs in parallel with new NTA Flow Storage Database until the migration has completed.

 

When upgrading to NTA version 4.4 or later, there are new requirements for the NTA Flow Storage Database. A separate Microsoft SQL database instance is required for flow storage. For production deployment, SolarWinds NTA requires the Standard or Enterprise edition of SQL Server 2016 SP1 or later for the NTA Flow Storage Database. Existing flow data from your current installation will not be migrated, and you will no longer have access to your flow data once you complete your upgrade.

 

 

 

Last modified

Tags

Classifications

Public