Hello, 650 servers Onepoint: - Data 2,000 - Log 10,000 SystemCenterReporting: - Data 85,000 - Log 18,000 this seems really far from the guide... OnePoint: - Data 2,000 - Log 1/3 of data which should be 700 but even with less than 5,000 it is full each time... the maintenanceplan runs... SystemCenterReporting: looks correct for the Data if we consider 395 days but I have 60 days only !!! and the log should be 3,500 if OnePoint was 7000 but as it is 10,000 should it be 50,000... (: http://blogs.technet.com/b/fcsnerds/archive/2008/09/25/fcs-with-mom-2005-database-guidance.aspx and it is full every other day !!! especially I have a 60 days grooming set to try to minimize the size!!! select cs.cs_tablename 'Table Name', wcs.wcs_groomdays 'Groom Days' from warehouseclassschema wcs join classschemas cs on cs.cs_classID = wcs.wcs_classID where cs.cs_tablename = 'SC_SampledNumericDataFact_Table' and wcs.wcs_mustbegroomed = 1 select cs.cs_tablename 'Table Name', wcs.wcs_groomdays 'Groom Days' from warehouseclassschema wcs join classschemas cs on cs.cs_classID = wcs.wcs_classID where cs.cs_tablename = 'SC_AlertFact_Table' and wcs.wcs_mustbegroomed = 1 select cs.cs_tablename 'Table Name', wcs.wcs_groomdays 'Groom Days' from warehouseclassschema wcs join classschemas cs on cs.cs_classID = wcs.wcs_classID where cs.cs_tablename = 'SC_EventParameterFact_Table' and wcs.wcs_mustbegroomed = 1 select cs.cs_tablename 'Table Name', wcs.wcs_groomdays 'Groom Days' from warehouseclassschema wcs join classschemas cs on cs.cs_classID = wcs.wcs_classID where cs.cs_tablename = 'SC_AlertToEventFact_Table' and wcs.wcs_mustbegroomed = 1 select cs.cs_tablename 'Table Name', wcs.wcs_groomdays 'Groom Days' from warehouseclassschema wcs join classschemas cs on cs.cs_classID = wcs.wcs_classID where cs.cs_tablename = 'SC_EventFact_Table' and wcs.wcs_mustbegroomed = 1 select cs.cs_tablename 'Table Name', wcs.wcs_groomdays 'Groom Days' from warehouseclassschema wcs join classschemas cs on cs.cs_classID = wcs.wcs_classID where cs.cs_tablename = 'SC_AlertHistoryFact_Table' and wcs.wcs_mustbegroomed = 1 Any idea? something does not seem right at least for the log files!!! Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Still the same numbers 650 servers Onepoint: - Data 2,000 - Log 20,000 otherwise it is failing each night!!! SystemCenterReporting: - Data 85,000 - Log 150,000 SCDWGroomJob is failing each night this seems really far from the guide... and still growing Where to look for pattern, clue? Thanks, DOm System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

?bump? any idea... why the logs are so big ...System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Log size will always be a function of how much work needs to be done. In a very busy system, this is not so big. For your grooming that is failing each night, you should manually run grooming, checkpoint, run it again. It may time-out, but each time it is grooming a little more. Get it down to a size where it is no longer timing out. Consider reducing the amount of performance and event log collection.Microsoft Corporation

Hello Dan, You say it is not so biig but for the documentation it seems far over... http://blogs.technet.com/b/fcsnerds/archive/2008/09/25/fcs-with-mom-2005-database-guidance.aspx Onepoint 2,000 seems okay for 600 servers but the log is supposed to 1/3 which would be 700 ... why am I having 20000, any new documentation or new stuff collected by FCS and filling up the logs? As is the log of SystemCenterReporting should be 5 times Onepoint log but 5 times 700 was supposed to 3500 but now with 20000 it should be 100000, and in both cases I am over also... no issue hidden behind this? I am rerunning the processes grooming and checkpoint now... but i need to make space at least the size of the log file as the first try failed for space not available.. the problem when I expand the log file it seems filling up as fast as the expansion is going... I ran the grooming 4 times already but the SystemCenterReporting is always filling up before ending... not sure the size is de4creasing as the file are growing... still in process.. Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Log size will always be a function of how much work needs to be done. In a very busy system, this is not so big. For your grooming that is failing each night, you should manually run grooming, checkpoint, run it again. It may time-out, but each time it is grooming a little more. Get it down to a size where it is no longer timing out. Consider reducing the amount of performance and event log collection. Microsoft Corporation Hello Dan, Finally I have a SCDWGroomJob running longer than before it started at 9:53 a.m. and it is still on-going now at 3:00 p.m. already 5 hours... it seems working... the SQL logs do not show any message as before Error 9002 which is a good sign... OnePoint - Database 2% Free Space - Data 23% (at 2 Gb) - Log 28% (at 20Gb) SystemCenterReporting - Database 7% Free Space - Data 20% (at 80 Gb) - Log 44% (at 150 Gb) As it is "Carmageddon" week-end in LA I am leaving the job running.... Still on-going Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Now it is 6:00 p.m. and the job is still running no timeout ??? Anything to check? I checked the Application log and already there is an issue here: og Name: Application Source: Microsoft Operations Manager Date: 7/15/2011 5:56:13 PM Event ID: 26027 Task Category: None Level: Warning Keywords: Classic User: NETWORK SERVICE Computer: voforefrontcs1.ad Description: The MOM Server is configured to use Mutual Authentication, but the MOM Agent at 10.32.157.76 is not. This is a misconfiguration and is typically caused by a manual agent install configuration that does not match the MOM Server. So i will try to identify the machines having this issue by a query on the database as not all machines are listed ... after first reading Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Now it is 6:00 p.m. 7/15/2011 and the job is still running no timeout ??? Now it is 11:00 a.m. 7/16/2011 and the job is still running no timeout ??? Job Monitoring says : Executing: 1(DWGroomingStep) SQL Logs: No trace of any start, any failure, any completion, any issue,... SQL Agent Logs: No trace of any start, any failure, any completion, any issue,... Anything to check? I checked the Application log and already there is an issue here: og Name: Application Source: Microsoft Operations Manager Date: 7/15/2011 5:56:13 PM Event ID: 26027 Task Category: None Level: Warning Keywords: Classic User: NETWORK SERVICE Computer: voforefrontcs1.ad Description: The MOM Server is configured to use Mutual Authentication, but the MOM Agent at 10.32.157.76 is not. This is a misconfiguration and is typically caused by a manual agent install configuration that does not match the MOM Server. So i will try to identify the machines having this issue by a query on the database as not all machines are listed ... after first reading Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Now it is 2:00 a.m. 7/17/2011 and the job is still running no timeout ??? Now it is 9:00 a.m. 7/17/2011 and the job is still running no timeout ??? Now it is 2:30 p.m. 7/17/2011 and the job is still running no timeout ??? Now it is 10:00 p.m. 7/17/2011 and the job is still running no timeout ??? some changes in the sizing ... OnePoint - Database 5% Free Space - Data 54% (at 2 Gb) - Log 99% (at 20Gb) SystemCenterReporting - Database 7% Free Space - Data 20% (at 80 Gb) - Log 46% (at 150 Gb) still running... trying to watch the grooming s close as possible ... Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, Finally it fails with the following error after 1 day and 16 hours !!! Date 7/16/2011 10:01:27 AM Log Job History (SCDWGroomJob) Step ID 1 Server VOFOREFRONTCS1 Job Name SCDWGroomJob Step Name DWGroomingStep Duration 1.16:30:53 Sql Severity 17 Sql Message ID 1105 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0 Message Executed as user: AD\svcffcs. Could not allocate space for object '<temporary system object: 422292005519360>' in database 'tempdb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. [SQLSTATE 42000] (Error 1105). The step failed. Reviewing this issue...adding a second filegroup... rerun the process.. Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, the grooming is runni ng again for the last 4 hours... now it is the tempdb.mdf file which is over 20 Gb!! is it expected... It seems I am carrying loads unexpectively!!! the tempdev is set 8 Mb with 10% growth now it is 20 Gb and even it shows 20 Gb and Free Space 20 Gb it is not possible to decrease its size... shrink is not doing anything... Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

I'm going to stick with guidance - just keep running it until it doesn't time out. What you can do is run it for an hour, kill it. Run it another hour, kill it. It is deleting things - but it appears that your DB grooming has reached a size where you grooming started to fail and then it got bigger after that. You will need to prune it in stages. Auto-grow can cause all kinds of problems with fragementation over time. When you are seeing a 20GB file with 8MB and 10% growth, think about the number of fragments that are there. (20GB - 8MB)/800K - more than 20K fragments. Microsoft Corporation

Thanks Dan, I will plan a grooming per hour and kill and go ... Also as the tempdb is filling up I think it is the only way to do it Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, The files Onepoint.mdf, Onepoint.ldf, SystemCenterReporting.mdf and SystemCenterReporting.ldf looks good now.... still some doubt about the SCDWGroom job as the tempdb.mdf is growing from 8 Mb to 200 Gb in an hour!!! Not sure it could run anytime by itself without creating new issues... Thanks, DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello, The files Onepoint.mdf, Onepoint.ldf, SystemCenterReporting.mdf and SystemCenterReporting.ldf looks good now.... for several days. I have still some doubt about the SCDWGroom and MaintenancePlan as they need to run manually with HIGH supervision as the tempdb.mdf is growing from 8 Mb to 200 Gb in an hour!!! Not sure it could run anytime by itself without creating new issues... Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

What is causing it to grow like this Dom? Is it forefront? Exchange 2010? Look for ways to make the amount of data that you don't need be reduced. Look at perf collection and event collection rules to see if you can turn some off to reduce the amount of data being saved.Microsoft Corporation

Hello Dan, it is Forefront Client Security which is running on this server... nothing else. let me review the data collection to see ... http://technet.microsoft.com/en-us/library/bb418780.aspx has been reviewed This article has been applied http://support.microsoft.com/kb/943556 but I discovered that the servers present in several Policy got only the last one applied by the GPO... (don't shoot the messenger!!)... is that true ? e.g.: SCOM Servers the root management server has also sql so it has an exclusion policy for SQL and one for Root management Server Could it be an issue? reviewing the MOM Console > Rule groups now 1. Mutual Authentication seems to be one Event issues a lot of data 2. Local Administrators group with more than 8 members as well.. Still progressing Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager