ok so I am getting the above alert and have tried to set the new Database size as described in previous posts i.e into SQL manager find the DB file and set to new size. I can verify the new SQL db file size by browsing to where the file is and looking at it and it is bigger. but then a given interval later, I haven' worked out how long, I get the same alert again i.e. Ops DB free space low. So what am I doing wrong, the file is again going back to a small size that is too small for me. Any ideas etc bearing in mind I have already tried setting the new size and that doesn't stay. Thanks RF RF

Sounds like there is a maintenance plan that has the Shrink DB option enabled. Check the maintenance plans on this SQL Server and make sure the Shrink DB option is not enabled. Hope this helps!Scott Moss MVP (Operations Manager) | President - System Center Virtual Users Group | Vice President - Atlanta Southeast Management Users Group (ATL SMUG) Please remember to click Mark as Answer on the post that helps you!

Also refer to the following article: ResearchThis! KB - Ops DB Free Space Low http://systemcentercentral.com/BlogDetails/tabid/143/IndexID/20352/Default.aspx 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.

Scott Thanks but unfortunately not that, would have been good if it was. RFRF

vivian I think thats what I dscribed above as having down already? RFRF

Hi Robin If the database is shrinking for no apparent reason then either: - the database is set to auto shrink - there is a SQL job or maintenance plan that is shrinking the database on a regular basis. - someone is manually shrinking the database Bring up a performance chart of the database and see when it is shrinking to see if that he helps. But OpsMgr isn't doing this. It is someone or something in your environment. Is it that the database size is shrinking back or just that the database is growing too quickly so that every time you grow the database, it fills up? Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Graham I agree with what you have written and will look for the performance chart you mentioned. The database file size is actually shrinking. I had a backup job running which had a shrink DB function init but I had set the job to retain space in DB, i.e. dont shriking the file. That was all deleted last night and I set the MOM_DATA file back to 5 Gig. This morning the MOM_DATA file is again 1. something Gig ............... So I shall find that chart and look. Thanks RFRF

Graham In the properties of the OpsMan DB on the Options > Automatic section the Auto Shrink option was set to true. Going to change this to false and see if that was casuing the issue. Just checked the Dev setup and that is set as false, so looks like I am to blame. Will leave for 24 hours and then get back to you guys. Thanks RFRF

Hi Robin That will be the cause - let us know tomorrow or later in the week if it is still happening. Not sure if you have see Kevin Holmans blog - he has some great articles about all things OpsMgr and one specifically about DB maintenance: http://blogs.technet.com/b/kevinholman/archive/2008/04/12/what-sql-maintenance-should-i-perform-on-my-opsmgr-databases.aspx Cheers GrahamView OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Graham All good here now, thank you very much for your help Graham. It was the DB marked to auto-shrink. Which is something I must have done, so user error again! :( Thanks once again. RFRF