• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

Error log: Starting Database (LOTS of log entries)

Hi all,

I have about 10 databases running at the same SQL Server 2000 instance. Everything works ok but I just had a look at the SQL Server error log and it really have a lot of lines like:

2007-10-02 06:38:48.35 spid72    Starting up database 'FileSend'.

When I say a LOT I really mean it..... like 1 per second or something like that!!!

Now, everything works..... even the filesend database and there are no other messages in the error log....
Should I worry or? I think i should right? ithis is not normal, but where do I start looking?

Thx a lot!
  • 2
1 Solution
Guy Hengel [angelIII / a3]Billing EngineerCommented:
every database is initially (on start up of sql server) started up explicitely. just to check if everything is fine.

now, if that continues through the day, then check if the mentionned databases are configured to "auto-close" (you can find that in the database properties). if they are, uncheck that setting.

that property will make sql server "close" the database if it has not been used for a certain while, and flush all it's data from the memory.
that does indeed free up memory, but in case the databases are still quite frequently used, it just kills the performance.
nicolajsbAuthor Commented:
LOL Thx a lot :-)

This is about the most stupid thing I have ever seen...... MUST mention that the DB was configured by a developer and not me ;-)
Guy Hengel [angelIII / a3]Billing EngineerCommented:
well, it's not a stupid option, per se, it has it's validity.
In practice, however, I have not see this in prod servers, only in test and dev servers...

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now