Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Patch Manager SQL Server database is growing too fast

Patch Manager SQL Server database is growing too fast

Overview

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

Environment

Patch Manager 2.1

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. 

Last modified

Tags

Classifications

Public