Trying to understand a bit more about the clean up process of the Segment table in SQL Server RS 2008 R2. We have been having an issue in rendering reports, the reports are very large and the ReportServerTempDB is growing significantly, it was up to 33 gig and 99.9% of the space was taking up by the Segment table. I did not change the CleanupCycleMinutes, have left it at 10. While watching the table yesterday after the process failed, I could see the clean up working for the first couple of rounds but then it did not clean anything and the number of rows in the Segment tabled remained constant over 500,000. This morning, I checked the table again, and it had cleaned out the table, to 0 rows. I reviewed the log files and could see this message at 4:19 am:
dbcleanup!WindowsService_1!e9c!08/28/2012-04:19:52:: i INFO: Cleaned 520665 unused segments.
I have a couple questions,
- What causes the dbcleanup!windowsservice to decide to run?
- Why would this have cleaned out the segment table and not the normal 10 minute cycle clean up
- What can I do to clean this data up if we continue to have space problems with the segement table, can I automate a more through clean up rather than waiting for the dbCleanup!Windowsservice.
THanks