putting the OM db into auto-grow will eventually lead to fragementation and poor performance that cannot be easily corrected. Instead of auto-grow, when you first create the DB, make it sufficiently large (disk space is dirt cheap) so that it has 14 days of room. I know, this takes some calculation and isn't as simple as auto-grow, but you will be really unhappy when the DB gets fragmented due to auto-grow file segments. Microsoft Corporation

putting the OM db into auto-grow will eventually lead to fragementation and poor performance that cannot be easily corrected. Instead of auto-grow, when you first create the DB, make it sufficiently large (disk space is dirt cheap) so that it has 14 days of room. I know, this takes some calculation and isn't as simple as auto-grow, but you will be really unhappy when the DB gets fragmented due to auto-grow file segments. Microsoft Corporation

Hi! I keep getting this elow alert. I see I have sufficient space on he drive and also set the DB to autogrowth. Operations Manager operational database percent free space is 23.59%. Ops DB Server Name: osmgr_1 Ops DB Name: OperationsManager. Can someone help me on resolving this issue? Many thanks Ven

Hi, Just to say that I'm also still getting this alert even if the % free space shows in the performance view is now over 40%. SCOM 2007 R2 CU5 Thanks Alain

Hi! Dan, Many thanks for the reply. SInce its too later for that - do you propose any way we can avoid getting this alert, preferably by resolving it? Ven

Hi, Check this link: http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/41318/Default.aspx "Alert: Ops DB Free Space Low Issue: The Operations Database for OpsMgr 2007 has less than 40% free space available. Resolution: OperationsManager database was not large enough to provide seven day (default) retention for the number of agents being monitored. Increased the size of the database using the SQL Server Management Studio (install it on the system running the OpsMgr console for ease of use). Connect to the server running the OpsMgr Operational database (shown in the alert), open the server/databases, right-click on the OperationsManager database (default name) and click Properties. Click on the Files tab, change the MOM_DATA size to the new size and click OK. You can validate the change in size occurred by going back to the properties of the database. The alert will resolve itself in Operations Manager in approximately 15 minutes if enough free space is available, as this monitor is defined to a 900-second frequency."Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.