Chances are, if you have an SBS 2008 server, it is running very well. But this may lead you to become complacent in managing the server. For example, it is important that you run the SBS 2008 Best Practices Analyzer on your server on a regular basis. Whether that is monthly, or quarterly, run it!
On a recent SBS 2008 server that has been chugging along quite nicely, I discovered that BPA had not been run in quite awhile. When I did, I was greeted with this warning:
The SBSMonitoring database is nearing maximum size
The SBSMonitoring database is currently 3762487296 bytes in size
Wow, that’s nice … except for the fact that the warning message doesn’t tell you what to do to fix it or clean it up. It doesn’t even point you to a KB article.
The rest of this blog post identifies three different solutions to this problem.
Solution 1: KB 981939
If you do your due diligence in searching the web, you will come across Microsoft KB 981939. You can read through the KB article for the details, and you may want to give it a try.
When you run their PowerShell script, you may get an error about the execution of scripts. If so, simply type the following command at the PS> prompt:
Set-executionpolicy remotesigned and press Enter
But, wait — there’s a second solution!
Solution 2: Replace SBSMonitoring Database
If solution 1 fails, and you go back to search the Internet, you will discover a blog post from Third Tier titled: SBS 2008 Monitoring Database Fills to Capacity.
This solution has you replacing the current SBSMonitoring database with a new clean one. Only one problem: how many people keep a clean copy of their Monitoring database around???
No problem, there’s a third solution, which is the best!
Solution 3: Recreate the SBSMonitoring Database
Check out the SBS Blog site for How to Recreate the SBSMonitoring Database.
Simply download the provided zip file, extract the PowerShell script, start up an administrative PowerShell session, and run the script. Voila! It’s finished almost immediately.
All that is left is to rerun the BPA and verify that the warning message no longer appears!