locked
Clustered SQL and "Alert only if service startup type is automatic" RRS feed

  • Question

  • Hi!

    Some questions/notes regarding SQL MP´s documentation

    1. In the latest version 6.1.314.35, on page 19 under "Customize the SQL Server Management Pack"; is it really necessary to override the basic service monitor parameter "Alert only if service startup type is automatic" for DB (not engine)? It could be an enormous work to create overrides for each DB on each clustered instance of SQL. If an override is in place for the service monitor on each "DB Engine" wouldn´t that cover it, as long as you do not have users that are scoped explicitly for alerts from DB only?

    Also, the first to sections, regarding "Full Text Search", should probably be removed since this monitor is disabled by default nowadays, right?

    2. In the older MP 6.0.6648.0, what is the default value of the parameter "Alert only if service startup type is automatic" for the SQL 2000 DB Engine Service
    State-monitor, the field is empty? I mean, should this be overridden with "False" on clustered instances also?

    Best regards
    PETER

    Friday, August 20, 2010 9:56 AM

Answers

  • By default, service monitors only monitor services where the startup type is set to automatic. In a cluster, it's set to manual, that's why the override is needed. I'm not very familiar with the SQL MP, but would assume it's ok to override the monitor per clustered instance of SQL. It does not seem to make sense to have the monitor running per database.
    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    • Marked as answer by Vivian Xing Friday, August 27, 2010 9:11 AM
    Friday, August 20, 2010 7:55 PM
  • if you have the cluster mp running i wouldn't override this setting at all. The cluster mp will report when a resourcegroup is (partially) offline and catching the condition where SQL is not running.

    http://blogs.technet.com/b/kevinholman/archive/2010/08/16/sql-mp-version-6-1-314-36-released-adds-support-for-sql-2008r2-and-many-other-changes.aspx


    Rob Korving
    http://jama00.wordpress.com/
    • Marked as answer by LTHPETER Monday, August 30, 2010 6:31 AM
    Friday, August 27, 2010 1:18 PM

All replies

  • By default, service monitors only monitor services where the startup type is set to automatic. In a cluster, it's set to manual, that's why the override is needed. I'm not very familiar with the SQL MP, but would assume it's ok to override the monitor per clustered instance of SQL. It does not seem to make sense to have the monitor running per database.
    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    • Marked as answer by Vivian Xing Friday, August 27, 2010 9:11 AM
    Friday, August 20, 2010 7:55 PM
  • hello again!

    I would very much like an answer to the second question also.

    Sincerely
    Peter

    Friday, August 27, 2010 9:15 AM
  • if you have the cluster mp running i wouldn't override this setting at all. The cluster mp will report when a resourcegroup is (partially) offline and catching the condition where SQL is not running.

    http://blogs.technet.com/b/kevinholman/archive/2010/08/16/sql-mp-version-6-1-314-36-released-adds-support-for-sql-2008r2-and-many-other-changes.aspx


    Rob Korving
    http://jama00.wordpress.com/
    • Marked as answer by LTHPETER Monday, August 30, 2010 6:31 AM
    Friday, August 27, 2010 1:18 PM