Ask a questionAsk a question
 

AnswerSQLSERVER 2005 Event Log

  • Monday, October 17, 2005 4:14 PMmrdomiscoding Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi

    Is there a away stop SQLEXPRESS from reporting the eventID : 17137

    Starting up database ... 

    In the windows Event Log.

    I understand that I can filter the events logs etc to remove this, and even have them re-cycle when needed, however I don't really care that the database has been startedup, I would rather know if the database failed to start.

    2 questions
    =========

    1) Can this behavouir been changed so that it reports failed startup, in the eventlog.

    2) If is it possible to disable the message that says it started up successfully, as it there are just too many of these being procedured, and quite frankly we don't care.



Answers

  • Wednesday, November 02, 2005 11:06 PMRoger_Wolter_MS Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    The short answer is no, you can't turn it off.  This message is pretty useful to PSS when they look at database problems so we don't provide a way to surpress it.  You might want to look at whether turning off the autoclose attribute makes sense for your databases.  That would eliminate most of these messages and provide quicker startup when you first connect also.  The down side to this is that SQL Express will consume more resources when you're not using it so you want to look at whether SQL Express is idle often enough so this might be an issue.

All Replies

  • Wednesday, November 02, 2005 11:06 PMRoger_Wolter_MS Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    The short answer is no, you can't turn it off.  This message is pretty useful to PSS when they look at database problems so we don't provide a way to surpress it.  You might want to look at whether turning off the autoclose attribute makes sense for your databases.  That would eliminate most of these messages and provide quicker startup when you first connect also.  The down side to this is that SQL Express will consume more resources when you're not using it so you want to look at whether SQL Express is idle often enough so this might be an issue.
  • Thursday, June 21, 2007 7:21 PMTed Manasa Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I was able to solve this problem with our databases (SharePoint dbs) using the ALTER DATABASE command:

     

    alter database [Database_Name] SET auto_close OFF