Current log - too much entries?

Hello,

does anyone know what could be wrong? There's a lot of similar entries
in the SQL Server current log:

2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'

There are hundreds of similar entries that repeat every few seconds. The
database works quite slowly and the users get 'Connection timeout'
message very often.

Thanks for any advice.

...:: fabio"Fabio" <fabio@.anti-spam.inet.alpha.pl> wrote in message
news:bumbod$d6c$1@.nemesis.news.tpi.pl...
> Hello,
> does anyone know what could be wrong? There's a lot of similar entries
> in the SQL Server current log:
> 2004-01-21 17:54:00.01 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:06.45 spid57 Starting up database 'DB_NAME'
> 2004-01-21 17:54:59.13 spid56 Starting up database 'DB_NAME'
> There are hundreds of similar entries that repeat every few seconds. The
> database works quite slowly and the users get 'Connection timeout'
> message very often.
> Thanks for any advice.
> ..:: fabio

Probably the database is set to autoclose - if there are no active
connections, then it is closed. That means when a connection is made, the
database is opened again, which takes time. You can check like this:

select databasepropertyex('DB_NAME', 'IsAutoClose')

1 means it's on, so you can turn it off like this:

alter database DB_NAME set auto_close off

Simon