Intermittently and overnight, I receive email alerts from SCE 2007 SP1 running on SQL Server 2005 Standard that say: Transaction log for database 'OperationsManager' is full and Could not write a checkpoint record in database ID 8 (OperationsManager) because the log is out of space By the time I run a SQL dbcc sqlperf(logspace) command hours later in the morning, nothing is full. What is even more perplexing is this database is NOT set up for full logging, it is set up for simple logging in SQL Server. What is going on here? J McNemar

Nicholas, Thank you for the reply. The link you sent included a link to this blog entry: http://blogs.technet.com/kevinholman/archive/2007/12/13/how-grooming-and-auto-resolution-work-in-the-opsmgr-2007-operational-database.aspx That blog entry refers to some built in maintenance done by the Ops Manager system on its databases. The time of day of that preconfigured maintenance schedule matches up to when I have the transaction log full problem, so I think I now know at least what is causing it. However, the article was of n use in suggesting why this is happening and how to prevent it. I did increase the size of my OperationsManager database and its transaction log based on some sizing recommendations in the article. We'll see if that helps with this issue and I will replay back with results, although it may take a few months to know if resizing helped, as this is a very intermittent problem.J McNemar

Nicholas, Thank you for the reply. The link you sent included a link to this blog entry: http://blogs.technet.com/kevinholman/archive/2007/12/13/how-grooming-and-auto-resolution-work-in-the-opsmgr-2007-operational-database.aspx That blog entry refers to some built in maintenance done by the Ops Manager system on its databases. The time of day of that preconfigured maintenance schedule matches up to when I have the transaction log full problem, so I think I now know at least what is causing it. However, the article was of n use in suggesting why this is happening and how to prevent it. I did increase the size of my OperationsManager database and its transaction log based on some sizing recommendations in the article. We'll see if that helps with this issue and I will replay back with results, although it may take a few months to know if resizing helped, as this is a very intermittent problem.J McNemar

Regarding the issue " Transaction log for database 'OperationsManager' is full”, please also refer to the following thread: Large OpsMgr database logfile http://social.technet.microsoft.com/Forums/en/operationsmanagergeneral/thread/115b6708-5e74-4b42-a237-919a255d551d Hope this helps. Thanks.Nicholas Li - MSFT 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.

Regarding the issue " Transaction log for database 'OperationsManager' is full”, please also refer to the following thread: Large OpsMgr database logfile http://social.technet.microsoft.com/Forums/en/operationsmanagergeneral/thread/115b6708-5e74-4b42-a237-919a255d551d Hope this helps. Thanks.Nicholas Li - MSFT 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.