Custom pollers consuming high tables

1) Well, I can't say that easily, because it depends on what is the UNDP polling...

2) It souldn't be a problem if your Pollers, Nodes, Bandwith, an Database can handle it

3) There sould be a way to do that and know wich one is consuming more space than others but I think you problem migh be general.

If there's a lot of data in "Custompollerstatisticsdetail" I think it means that you have your Polling Settings for Detailed Data for UNDP with a lot of time.  These are the default settings. http://www.solarwinds.com/documentation/en/flarehelp/npm/content/core-polling-settings.htm?cshid=OrionPHResourcePollingSettings

If that's your case, there are some KB's that says that you should adjust those settings for something that your DB can handle.
Remember that if you replace the 3 days default setting for something like 14 days, you should not change that setting straight to 3 days again, cause you DB mantenance would have a lot of work to do. You should do it in some way that would have lowest affectation to the db maintenance.

Hope it helps you.

Peter.

1) Well, I can't say that easily, because it depends on what is the UNDP polling...

2) It souldn't be a problem if your Pollers, Nodes, Bandwith, an Database can handle it

3) There sould be a way to do that and know wich one is consuming more space than others but I think you problem migh be general.

If there's a lot of data in "Custompollerstatisticsdetail" I think it means that you have your Polling Settings for Detailed Data for UNDP with a lot of time.  These are the default settings. http://www.solarwinds.com/documentation/en/flarehelp/npm/content/core-polling-settings.htm?cshid=OrionPHResourcePollingSettings

If that's your case, there are some KB's that says that you should adjust those settings for something that your DB can handle.
Remember that if you replace the 3 days default setting for something like 14 days, you should not change that setting straight to 3 days again, cause you DB mantenance would have a lot of work to do. You should do it in some way that would have lowest affectation to the db maintenance.

Hope it helps you.

Peter.

This will get a breakdown of how many row are associated with each poller and what their interval is set to. I ran into similar problems in the past and in almost all cases when I brought it up to the owners of those systems i get answers like "Oh we didn't even realize SW was collecting that, we had trouble with it like 5 years ago but it's not an issue anymore, we don't need it."

select c.uniquename, count(*) as DB_Rows, case when c.PollInterval=0 then 9 else c.PollInterval end as interval
from custompollers c
join custompollerassignment cpa on c.CustomPollerID=cpa.custompollerid
join custompollerstatistics_detail d on d.CustomPollerAssignmentID=cpa.CustomPollerAssignmentID

group by c.uniquename, c.PollInterval

order by DB_Rows desc