DB Maintenance for OPS MGR DB

Thank you for the response Anders.
> >
> > I've read that thread, the issue is that we did not have a maintenance
> > plan setup and the log file hit a full warning.  We setup a plan to
> > shrink it some and now we still hit log full warnings and we get db
> > free space warnings.
> >
> > Right now the log file is 1gb - this to me seems extremely large.  Is
> > this normal?  I am OK with not shrinking the db / log file if this is
> > just an initial growing point to get it to a stabilized level - we
> > recenly put more agents on and the log file has filled up.
> >
> > I can bump the log file to 2gb and see how it goes but I also am
> > curious if this log file will grow continuously or if it will
> > eventyally stabilize.
> >
> > Thanks,
> >
> > "Anders Bengtsson [MVP]" wrote:
> >
> >> Hello Jake,
> >>
> >> Please take a look at this thread
> >> http://www.eggheadcafe.com/conversation.aspx?messageid=31051404&threa
> >> did=31051404
> >>
> >> Anders Bengtsson
> >> Microsoft MVP - System Center Operations Manager
> >> www.contoso.se
> >>> Hello -
> >>>
> >>> On our OPSMgr Database, we hit a Logfile Full warning.  Our DB is
> >>> not set to autogrow, nor is the log.
> >>>
> >>> If we set up a Maintenance plan to shrink the db after backup, the
> >>> DB goes into a 40 % free warning.
> >>>
> >>> I am wondering what the Best Practice is for this is?  I can set the
> >>> autoshrink after backup to be 50% - but this seems like a wasteful
> >>> practice.
> >>>
> >>> Running SQL 2005 64bit on Win2k8 64bit
> >>> Please advise---