Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

Browse by Tags

Related Posts
  • Blog Post: OpsMgr 2012 – Grooming deep dive in the OperationsManager database

    Grooming of the OpsDB in OpsMgr 2012 is very similar to OpsMgr 2007.  Grooming is called once per day at 12:00am…. by the rule:  “ Partitioning and Grooming ” You can search for this rule in the Authoring space of the console, under Rules. It is targeted to the “All Management Servers Resource...
  • Blog Post: Boosting OpsMgr performance - by reducing the OpsDB data retention

    Here is a little tip I often advise my customers on..... The default data retention in OpsMgr is 7 days for most data types:     These are default settings which work well for a large cross section of different agent counts.  In MOM 2005 - we defaulted to 4 days.  Many customers,...
  • Blog Post: Grooming process in the Operations Database

    This is a continuation of my other post, on general alert grooming: How grooming and auto-resolution work in the OpsMgr 2007 Operational database   Grooming of the OpsDB is called once per day at 12:00am…. by the rule:  “ Partitioning and Grooming ” You can search for this...
  • Blog Post: What SQL maintenance should I perform on my OpsMgr databases?

    This question comes up a lot.  The answer is really - not what maintenance you should be performing... but what maintenance you should be *excluding*.... or when.  Here is why: Most SQL DBA's will set up some pretty basic default maintenance on all SQL DB's they support.  This often includes...
  • Blog Post: Understanding and modifying Data Warehouse retention and grooming

    You will likely find that the default retention in the OpsMgr data warehouse will need to be adjusted for your environment.  I often find customers are reluctant to adjust these – because they don't know what they want to keep.  So – they assume the defaults are good – and they just keep EVERYTHING...
  • Blog Post: How grooming and auto-resolution work in the OpsMgr 2007 Operational database

    How Grooming and Auto-Resolution works in the OpsMgr 2007 Operations DB Warning – don’t read this if you are bored easily. In a simplified view to groom alerts….. Grooming of the ops DB is called once per day at 12:00am…. by the rule: “ Partitioning and Grooming ” You can search...
  • Blog Post: Tuning tip – turning off some over-collection of events

    We often think of tuning OpsMgr by way of tuning “Alert Noise”…. by disabling rules that generate alerts that we don't care about, or modifying thresholds on monitors to make the alert more actionable for our specific environment. However – one area of OpsMgr that often goes overlooked, is event overcollection...
  • Blog Post: Print Server management pack fills the Operational DB with TONS of perf data

    This is something I have noticed in MOM 2005, and seems to be the same in the conversion MP for OpsMgr 2007.  (Version 6.0.5000.0 of the Microsoft.Windows.Server.Printserver (Converted) MP).  When you import this MP, it will fill the Operational and reporting databases with performance data...
  • Blog Post: Failed tasks aren't groomed from the Operational Database

    This appears to be present up to RC-SP1 version, build 6.0.6246.0   In the Task Status console view - I noticed an old failed task from 2 months ago..... however, my task grooming is set to 7 days.   To view the grooming process: http://blogs.technet.com/kevinholman/archive/2007/12/13/how-grooming...