I think they broke it up to load graphs faters.
1 of 1 people found this helpful
The FG1 stores the FlowCorrelation Pre/Post table
FG2 - SearchBy Tables
FG3 - Summary 1,2,3 Tables
FG4 - Details tables
By dividing the database in filegroups, it allows SQL Server a lot more freedom in how it grows these different files. It also gives customers who are seeking to improve their performance further, the ability to move these filegroups on different diskdrives. Finally, one customer request that we've seen, is for all there NetFlow data to be located in another database. Although, we decided not to move it into another database at this point in time, we tried to accomidate part of their request, by using filegroups. They then can store their netflow database on another disk.
Thanks that does help! So should everything have moved to the new filegroups because my old primary filegroup still has tables in it. Are these no longer needed or should they be relocated to one of the new filegroups? Here is a listing of some (not all) the tables and their filegroups.
No. Most of the tables should still live in the PRIMARY filegroup. Only the large sized NTA tables have been moved off into these new filegroups. The tables listed here are in their proper filegroups.
thanks David. I think I have what I need for our DBAs. the changes made to netflow from 3.x to 3.1-SP1 has really improved reliability and performance of both Orion and it's Netflow analyzer.
I have a question about these new filegroups. I have uninstalled netflow, and either deleted or truncated all of the netflow-related tables. However, the FG1 and FG3.mdf files are still huge and I need to get rid of that data. I was told by SW not to mess with the new filegroups, just to delete/truncate the netflow-related tables. How can I reclaim the space? I am assuming that only netflow data is in these FG#.mdf file groups. Thanks.
If you have deleted the data from the tables contained within those filegroups, then performing a shrink on those filegroups should reclaim the space. You can do this from Management Studio, by right clicking on the database then Tasks\Shrink\Files. This brings up the "Shrink File" dialog. Then in the Filegroup combobox, select the filegroup to shrink and hit Ok.
Personally, I 'm a little confused by this response. Can NetFlow data be stored in a database that is physically separate from the Orion database, or must it still be installed in the same physical location?
Are you actually talking about the ability to install the FGs on independent disks of a RAID array as long as the array is the one that Orion is on?
Finally, does you answer apply to 3.1 and 3.5?
Thanks you for clarifying this, because that documentation is indeed extremely deficient in this area.
NetFlow data still (including 3.5) is in the same database as Orion, but because it now lives in different FGs, can be stored on other disks. There is no SQL Server requirement that FGs must live on the same RAID array. Now, keep in mind that this technique is an advanced database topic and the ability is not provided within the Orion or NetFlow user interfaces. It would be best for a database administrator to move these filegroups to separate locations, if that is what you desire.