One of my SQL engineers is asking what counters the top 2 tables (below) are associated with? There seems to be a lot of records so we need to verify if the application is purging old data.
Let me guess... (fingers on a wind) ... the top one is associated with components and bottom one with ports... I think...
On a serious note - purging of data is configurable in settings as "statistic retention" periods: SETTINGS > POLLING SETTINGS. You have time stamp in ComponentStatus table - so you can check this one easily. The amount of data will depend on the number of components that you have and how frequently you poll them.
alexslv is correct. These tables should not be purged through SQL Management Studio, but rather controlled through the database retention settings in the web interface. Once daily maintenance is run that evening, all records older than defined in the database retention settings (90 days by default) will be properly removed from the database. As you probably guessed, the APM_ComponentStatus_Detail table stores the historical availability for each component. The APM_PortEvidence_Detail table stores the result from each polled synthetic experience monitor for the last 7 days by default (user configurable). This includes (but is not limited to) HTTP, HTTPS, POP3, IMAP4, SOAP, TCP, FTP, DNS, etc. etc. monitors.
Many thanks for the explanation.
"The APM_PortEvidence_Detail table stores the result from each polled synthetic experience monitor for the last 7 days by default (user configurable)"
With that said, which retention setting controls this table? or is it affected by the global retention setting? (no granularity)
It's subject to the same retention as you have for all the other sam component monitors as you would find under the sam settings > database retention area.
