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
Last published date
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
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
- 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
Total CustomPollerAssignmentID 1070045661 77AFC200-EC56-4F52-9C77-CB5EFE4BA697 100024 54FEA200-AB56-4B52-9A53-CB5EFE4BA697 11224 2548AB56-4B52-9A53-CB5EFE4BA697 322 3AE542D3-2A56-8A53-CB5EFE4BA697 - Run the following query to find which nodes are assigned to that poller:
Select * from CustomPollerAssignment Where CustomPollerASsignmentID='ID'
CustomPollerAssignmnetID AssignmentName CustomPollerID NodeID 9DA098CC-1BED-4DBE-9D89-08856BA6AB3B ciscoEnvMonTemperatureStatusValue on Bas-2621.lab.tex 61A9A17E-29FC-4077-9367-A3114B48E23B 59 - Disable Historical Data on that Poller or unassign that poller.