Thank you for the response. I have over 600 instances and the reports do not seem to run off a EPMF with so many instances in it. These are just my production instances. We have a team of primary DBAs that each manage a certain group of instances. We have
a separate repository where each instance is associated with a primary DBA. I have a perl script that sends each DBA their daily report, using the info in PolicyHistoryDetail.
I am not opposed to using the reports. I can make the same connection using the supplied reports, but I think the DB is just to big. It is currently 220GB in size and I purge PolicyHistory every day to keep only 7 or 14 days worth of info. PolicyHistory
is at 90GB and PolicyHistoryDetail at 120GB. I can purge PolicyHistory even more, but I do not believe the reports use it at all.
I have to admit, I have not looked at tuning the SQL at all, so if you have a few 'off-the-top-of-your-head' ideas, let me know.
When I leave the reports to see if they will complete, I will eventually run out of space on either log space or TempDB (not sure which one now).
Any advice will be appreciated. Is it really necessary for all the info in PolicyHistoryDetail? Why do I care about a failure from a year ago?
Thanks in advance.