Operations Manager Database - Autogrow

Hi Brian,

 

To answer your questions:

 

1. Yes, OM2007 R2 is most definitely supported by the F5 Networks Management Pack.

 

2. Our service is not directly editing the SCOM database. It actually uses the SCOM SDK to record all data.

 

3. This one is a bit stickier, but hopefully I can give you a satisfactory answer. By default Microsoft says to leave autogrow off. This is the best practice, and I stand behind that; however, the amount of data typically collected by Operations Manager that is stored in the database before being sent to the data warehouse is pretty minimal compared to the size of the database. Our problem is that our service has the potential to collect hundreds of metrics per second, whereas Operations Manager normally collects a few dozen metrics per minute. So the volume of data coming in could potentially tip over the Data Warehouse if autogrow was not enabled. That is why we enable autogrow by default, seeing as best practices had a completely different picture in mind. This was a design decision on our end to give you the most complete picture of your network health at any given time, and this doesn't mean you can't follow Microsoft's best practices, but by doing so, you will have to be a lot more conscious of your dw db size, as well as the amount of data coming in from the F5 devices. If you can balance this, you should be able to still follow the Microsoft best practices.

 

If any of this doesn't make sense, or you have more questions, feel free to ask.

 

-Dave