We have a rather large NTA roll out (about 1590 flows per NPM) and upgraded to 3.6 yesterday morning with NPM 9.5.1. The upgrade went rather well but we did run into one problem with NTA. Originally with NTA 3.5 we worked very close with SW because we were running into problems with our Netflow information not displaying on the web. Turns out we were getting up to 50+ dbo's per node in our database which was causing locking conditions and other problems in the DB. Old dbo's weren't getting cleaned up and that just hosed everything up. Long story short we worked with SW and they gave us this query (below). We needed to run this query on the DB after our upgrade to 3.6 NTA because the dbo's were around 30+ per node id (and growing) in the database. Even thought NTA was saying netflow data was being received we weren't able to see it via the web or in the database.
If you happen to run into this problem you might want to try the following. Shut down all services within NPM. log into the database and run the following SQL. This will delete those dbo's. This SQL ran for about 20 minutes on 2 of our NPM that each have about 1500+ flows reporting to them. After the SQL is completed restart the services. Hopefully that will correct the problem it did ours. We have now been running about 18 hours on 3.6 and things seem to be stable.
DECLARE @script nvarchar(max), @doBreak int
SELECT @script = '', @doBreak = 0
SELECT TOP 1000 @script = @script + (CASE TABLE_TYPE WHEN 'BASE TABLE' THEN ' DROP TABLE ' WHEN 'VIEW' THEN ' DROP VIEW ' END) + TABLE_NAME + ' '
FROM INFORMATION_SCHEMA.TABLES WITH(NOLOCK) WHERE TABLE_NAME LIKE 'NetFlowDetail[_][0-9]%'
EXEC sp_executesql @script
SELECT @doBreak = (CASE WHEN LEN(@script)>0 THEN 0 ELSE 1 END)
SELECT @script = ''
Hope this works for you as well