SQL Monitor 3.3.X Purge Settings Issue
To fix this I had to change the Purge settings back to NEVER PURGE and restart SQL Server so as to shrink tempdb back down. Twice IÃ¢â‚¬â„¢ve done this and both times tempdb blew up and so I know for a fact that changing the Purge settings is causing this issue.
Does anyone know if there is any way to either control how the purge is done or to calculate in advance how much space the tempdb needs so that IO can adjust the drive space and then re-do the purge settings? I am at the point where IÃ¢â‚¬â„¢d like to purge some of the data that is beyond 1 year but I canÃ¢â‚¬â„¢t till I know what tempdb will need to get the job done.
PS Ã¢â‚¬â€œ If RedGate support has some tool/script/query that can be used to manually purge older data IÃ¢â‚¬â„¢m happy to take a look at it.