Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been doing an audit of my SQL Server log, as I 'thought' it was locked down but appeared to be open and we were getting a lot of password attempts on the SA account.

After sorting that, I have noticed throughout the day in the ErrorLog I have entries like this

2012-04-20 09:45:13.08 spid81      Starting up database 'DatabaseNameOne'.
2012-04-20 09:48:45.23 spid65      Starting up database 'DatabaseNameTwo'.
2012-04-20 09:53:58.16 spid143     Starting up database 'DatabaseNameFour'.
2012-04-20 09:54:28.24 spid151     Starting up database 'DatabaseNameFive'.
2012-04-20 09:54:47.04 spid152     Starting up database 'DatabaseNameSix'.

For all the databases on the server. Its doing this more or less every hour? Is that right? I assumed once the database had started thats it unless I restart the SQL service or shut down the server?

Any advice appreciated - Thanks.

share|improve this question
up vote 4 down vote accepted

Check to see if Auto Close is set to true.

If it is this closes the database when the last connection is closed, basically makes it go to sleep. It will fill your log up with those messages if it is left enabled. Best practice, unless needed, is to set it to false for all databases.

share|improve this answer
Thanks, half were still set as true for some reason! – leen3o Apr 21 '12 at 7:40

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.