Security Compliance

Patch Manager SQL Server database is growing too fast

This article addresses an issue that causes the Microsoft SQL Server database for Patch Manager to grow at an unusual rate.

First published date

10/17/2018 10:21 PM

Last published date

10/17/2018 10:21 PM

Overview

The Microsoft SQL Database for the Patch Manager Primary Application Server is growing at an unusual rate. 

Product section

Patch Manager

Cause

  1. The dbo.dt_wmi_Win32_WUAUpdateHistoryEntry table in the SQL Server database is not purging previously collected inventory data. 
  2. Found following tables taking up about 100+ GB together. 
    [EminentWare].[dbo].[dt_wmi_Win32_WindowsAdvancedFirewallRule] 
[EminentWare].[dbo].[dt_wmi_Win32_Service]
[EminentWare].[dbo].[dt_wmi_Win32_Process]
[EminentWare].[dbo].[dt_wmi_Win32_SystemDriver]​
  3. The Inventory task is not removing previously collected data and creating duplicate entries.

Resolution

  1. Delete the current computer inventory task(s).
  2. Create a new computer inventory task. In the Inventory Configuration page, deselect the tables that are huge and run the inventory task. This should empty the tables.
  3. Run the inventory tasks again and re-select the tables except the ones referred in 2nd cause above.  As these tables not required for patch reporting/auditing.

 

Contact your database administrator to truncate the database table and minimizing the database size.