Effect on SCOM DB size by changing recovery mode full to simple
Sorry this is long winded... I'm new to my current environment and to SCOM tuning (SQL Server 2005. The OpsManager DB was around 15GB with a tran log which would sometimes grow to around 9GB due to conflict with an existing maint plan which was rebuilding the indexes. I removed Opsmanager/OpsManagerDW from the existing maint plan to stop the log growth and allow the builtin SCOM maintenance to handle grooming etc. I changed the recovery mode for OpsManager/OpsManagerDW from full to simple mode per Kevin Holman's articles. Also per his articles, I gave OpsManager its own index rebuild maint plan. Now Opsmanager is around 26GB with free space around 11GB. It now almost consumes all the disk space allocated on the volume. (Unforetunately, I didn't have a good baseline so I don't know what free space the DBs had prior to changing full to simple.) So in general, does a DB grow that much and require that much free space when recovery mode is changed from full to simple? Can I shrink the database to reduce the amount of free space which seems alot? Should I get rid of the new weekly index rebuild job? Thanks.
March 17th, 2011 7:22pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics