SCOM 2012 R2 Autogrowth settings are static!

SCOM 2012 R2 Autogrowth settings are static!

After using SCOM 2012 R2 for a few weeks we started to get “Free Space Low” alerts for it’s own databases.

On investigation the default SQL instance has been setup with Autogrowth set to None.  So remember to change this to something more appropriate after installation or you’ll soon run into some issues.

As a minimum I changed the settings to be:

MOM Data 
Initial size: 5000MB
Autogrowth: 1000MB, unlimited

MOM Log
Initial size: 1000MB
Autogrowth: 100MB, unlimited

Please follow and like us:
0

2 thoughts on “SCOM 2012 R2 Autogrowth settings are static!

  1. I'm not a SCOM guy (ConfigMgr is my home!), however, I feel like I've read something about not using Autogrowth due to a performance issue with SCOM.

    Causes slowdowns due to fragmentation and you can end up with a massive DB.

    Check these blogs out:

    http://blog.coretech.dk/kra/autogrowth-setting-in-scom-2012-r2-are-pretty-static/

    http://thoughtsonopsmgr.blogspot.com/2011/01/scom-r2-am-i-healthy-part-iii-are-dbs.html

    http://blogs.technet.com/b/momteam/archive/2012/04/02/operations-manager-2012-sizing-helper-tool.aspx

  2. Hi, Thanks for your feedback. Your right, autogrowth can cause headaches and lead to large databases. The "out the box" settings for the SCOM database aren't sufficient though, we quickly outgrew them. I've set ours as above for the moment to allow us to configure our SCOM environment as it needs to be without having space issues.

    Something I'll hopefully go back and redress when time allows. 😉

Comments are closed.

Comments are closed.