Operations Manager Database - Autogrow

Hey Brian,

 

So just to clarify, we aren't collecting data specifically on the SCOM DB, that is just the sql server we know to exist because of the SCOM DB. In reality, the SQL configuration page was designed to collect information for where to put our own F5 database, which stores f5 device information and some other static data. The only time we come close to touching the SCOM DB is if the autogrow checkbox is marked. Other than that, we never touch either of the Operations Manager DBs.

 

 

As far as 2 is concerned, you are correct, I referred to the data warehouse when I should have said the SCOM db. The data warehouse is actually set to auto grow by default by Microsoft on a typical deployment. So my real recommendation is to leave them as configured by Microsoft, but increase the size of the SCOM DB to prevent any issues with too much data coming in before being archived in the data warehouse. We have a lot of data coming in from the F5 devices, so as a preventative measure, we enable autogrow to prevent data loss. The most performant solution is to manually increase the DB size initially and watch to see how big it grows when the f5 devices are pumping in the statistics you want to collect and balance from there. That way you still can follow MS best practices.