Before you embark on the migration, a couple of things worth checking
- I always check real-time access scanning software like McAfee or Symantec endpoint protection. Make sure there are exclusions for the solarwinds folders - SolarWinds Knowledge Base :: What files and directories should I exclude from antivirus protection to optimize performan…
- See the valuable tip from bsciencefiction.tv over here Re: What aspect of Orion/NPM do you find most annoying?. That seems to have made a significant difference for nickzourdos as well.
- If you are already on a 64 bit machine, you can use another disk partition on the NPM server for the Flow Storage DB. You will definitely see significant gains in the performance from NTA v3.x to NTA 4.x, and the demands on the SQL server drop significantly as well. You will need additional RAM to process the flow records and handle the FSDB though. All your upgrade options are discussed here http://knowledgebase.solarwinds.com/kb/questions/5071/NTA+4.0+Installation%3A+Frequently+Asked+Questions.
- Lastly, you will want to know for sure if the issues are originating out of the hypervisor layer. And, I would start from the database layer. You can download a free trial of Database Performance Analyzer SQL Server Performance Monitor | SolarWinds. It is super quick to set it up, and let it run for a day or two. And, see which Wait types are the top offenders. The new Storage IO tab also helps you determine if it was a disk latency issue.
