This week I had the honour of speaking at Silect’s MP University and my hot topic was Cookdown’s free PowerShell Authoring MP. I was looking to make the session a little fun, in homage to the original “Fun SCOM Monitoring” video from CTGlobal on monitoring a coffee machine with SCOM 2007 R2. So, I thought what’s the next best thing after coffee? Beer!

A company’s data warehouse is usually the largest database a company uses when dealing with SCOM data, this means it is often the most expensive to manage and maintain. They can also be a drain on your infrastructure, taking a long time to backup, slowing down reporting, consuming more hardware space and can be very time consuming to recover, if they go down.

Typically when tuning SCOM we talk about saving time and reducing alert noise, but today I’m going to make a quick post on saving database space through tuning. If you’d like to get an idea of what your current database usage is, take a look at this tool from scom2k7.com. This will give you a breakdown of where space is used in the SCOM Data Warehouse.