Our PA Filesight SQL Server database has grown to a very large size. It is currently at 186GB. I do not know how long it's been increasing to so large, it only became apparently recently due to us running low on storage space. I'm new to managing this product so need some direction to figure where to determine where the large data may be allocated. Our DB Admin did some shrinking on the database, but it only improved it slightly (saving a few GB of space). We are running v9.5.0.136 of File Sight
1 Answers
PA File Sight can definitely collect and store a lot of data. A few things to check:
- Look in Settings > Database Settings > Database Cleanup to see how long the data is being kept. Of course the longer it is kept, the more space is needed.
- Look at each of the monitors, especially the Ignore tabs. Make sure backend processes that you don't want to track are ignored, such as backup, search indexer, anti-virus, etc. That can cut down on a large amount of I/O that doesn't need to be stored. Also look at the user accounts - if there are service accounts that don't need to be tracked, ignore them.
- I'm going to make up a stat - about 80% of file I/O are reads. Most people do need to track reads for their use case but if you don't need them, not recording them to the database makes a huge difference.
If this doesn't help contact us at support at poweradmin.com and we'll dig further.
Related