Network Management

CustomPollerStatistics Tables are very large

The CustomPollerStatistcs tables are very large and this is impacting Database Query Performance or our Database Maintenance.

First published date

10/19/2018 8:54 PM

Last published date

8/23/2022 8:47 PM

Overview

This article details an issue in which the CustomPollerStatistcs tables are very large and are impacting Database Query Performance on Database Maintenance. 

  • dbo.CustomPollerStatistics_Detail
  • dbo.CustomPollerStatistics_Hourly
  • dbo.CustomPollerStatistics_Daily

Product section

Network Performance Monitor

Cause

The CustomPollerStatistics table stores historical data from Custom Pollers (Universal Device Pollers). A single tabular Poller is capable of returning 1000's of rows.

 

Resolution

  1. Run the following SQL query to identify the pollers with the most data:
    select count(*) as total,  custompollerassignmentid from custompollerstatistics_detail
    group by custompollerassignmentid
    order by total desc
    TotalCustomPollerAssignmentID
    107004566177AFC200-EC56-4F52-9C77-CB5EFE4BA697
    10002454FEA200-AB56-4B52-9A53-CB5EFE4BA697
    112242548AB56-4B52-9A53-CB5EFE4BA697
    3223AE542D3-2A56-8A53-CB5EFE4BA697
  2. Run the following query to find which nodes are assigned to that poller:
    Select * from CustomPollerAssignment
    Where CustomPollerASsignmentID='ID'
    CustomPollerAssignmnetIDAssignmentNameCustomPollerIDNodeID
    9DA098CC-1BED-4DBE-9D89-08856BA6AB3BciscoEnvMonTemperatureStatusValue on Bas-2621.lab.tex61A9A17E-29FC-4077-9367-A3114B48E23B59
  3. Disable Historical Data on that Poller or unassign that poller.