Overview
You may notice that a table named ProcessDetail in your scan results database is very large (eg: over 8 million records and over 800 MB in size), and wonder whether there is a way to reduce its size.
Solution
This table is responsible for enumerating the processes in the Dashboard > System Information tab.
If you do not require a historical record of this information, there are 2 ways we can further reduce the database size:
- You can delete all the entries in the ProcessDetail table using the
delete from ProcessDetailquery on the LanGuard scan results database, as shown in the animated GIF image below. Make sure you close the LanGuard console and stop the Attendant service before modifying the database. Shrink the transaction log beforehand. It is safer to usedelete top (500000) from ProcessDetailinstead, if you have over 10 million rows in this table, so the log does not fill up.
Implications: All processes will disappear from the Dashboard > System Information tab.
- In the event that the scans fill up the table too quickly and a regular manual cleanup job is not feasible, it is possible to configure the Full Scan profile (or any other active profile that collects this data) to not scan for objects that cause the ProcessDetail table to be populated. To do this, edit the profile as shown below (Creating and Personalizing a Scanning Profile). Note that the scanning profiles editor is laggy by default, and this lag has nothing to do with the SQL database size.
After making the changes, use thedelete from ProcessDetailquery on the LanGuard scan results database to clear the ProcessDetail table. It should not be populated again.
Implications:- Processes will not be collected in the Dashboard > System Information tab.
- No information will be collected for the Dashboard > Software tab. This includes antivirus and firewall detection, along with unauthorized application detection (if you have set up any).
- It will not affect patch detection.