Repeated 'Starting up database' messages

Hi,
Our network monitoring software reported the following message :
The database "MSCRM" in the instance "MSSQLSERVER" is in a critical state.
The state is: Suspect
After looking at SQL Enterprise Manager, the database appears to be fine and
I can browse tables, views, stored procedures and query the database as
normal. However when I looked at the SQL Server Error Log I found many
messages reporting 'Starting up database 'MSCRM'.
Any ideas?
Jonathan
Here is a sample log from this morning :
2004-07-02 09:29:53.76 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:54.48 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:59.17 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:59.43 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:59.67 spid89 Starting up database 'MSCRM'.
2004-07-02 09:29:59.93 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:00.24 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:00.48 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:00.82 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:01.06 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:01.46 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:01.74 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:02.03 spid89 Starting up database 'MSCRM'.
2004-07-02 09:30:02.32 spid89 Starting up database 'MSCRM'.
2004-07-02 09:32:19.81 spid89 Starting up database 'MSCRM'.
2004-07-02 09:45:00.48 spid72 Starting up database 'MSCRM'.
2004-07-02 09:45:01.06 spid72 Starting up database 'MSCRM'.
2004-07-02 10:00:00.23 spid91 Starting up database 'MSCRM'.
2004-07-02 10:00:00.65 spid91 Starting up database 'MSCRM'.
2004-07-02 10:00:00.89 spid101 Starting up database 'MSCRM'.
2004-07-02 10:00:01.60 spid101 Starting up database 'MSCRM'.
2004-07-02 10:00:06.99 spid91 Starting up database 'MSCRM'.Turn off autoclose for the database. What probably happened is that you have autoclose, some other
process (like anti-virus) got hold of the file while SQL Server didn't have it opened, SQL server
tried to access the file, ouch!, suspect database. Next restart, file weren't open by other process,
SQL Server turned off the autoclose option.
Autoclose is not designed for production databases!
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jonathan Wareham" <JonathanW@.CooperParry.com> wrote in message
news:OHdeeaBYEHA.644@.tk2msftngp13.phx.gbl...
> Hi,
> Our network monitoring software reported the following message :
> The database "MSCRM" in the instance "MSSQLSERVER" is in a critical state.
> The state is: Suspect
> After looking at SQL Enterprise Manager, the database appears to be fine and
> I can browse tables, views, stored procedures and query the database as
> normal. However when I looked at the SQL Server Error Log I found many
> messages reporting 'Starting up database 'MSCRM'.
> Any ideas?
> Jonathan
> Here is a sample log from this morning :
>
> 2004-07-02 09:29:53.76 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:54.48 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:59.17 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:59.43 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:59.67 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:29:59.93 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:00.24 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:00.48 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:00.82 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:01.06 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:01.46 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:01.74 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:02.03 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:30:02.32 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:32:19.81 spid89 Starting up database 'MSCRM'.
> 2004-07-02 09:45:00.48 spid72 Starting up database 'MSCRM'.
> 2004-07-02 09:45:01.06 spid72 Starting up database 'MSCRM'.
> 2004-07-02 10:00:00.23 spid91 Starting up database 'MSCRM'.
> 2004-07-02 10:00:00.65 spid91 Starting up database 'MSCRM'.
> 2004-07-02 10:00:00.89 spid101 Starting up database 'MSCRM'.
> 2004-07-02 10:00:01.60 spid101 Starting up database 'MSCRM'.
> 2004-07-02 10:00:06.99 spid91 Starting up database 'MSCRM'.
>|||Many thanks Tibor!
Jonathan
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23U0H0dBYEHA.3156@.TK2MSFTNGP12.phx.gbl...
> Turn off autoclose for the database. What probably happened is that you
have autoclose, some other
> process (like anti-virus) got hold of the file while SQL Server didn't
have it opened, SQL server
> tried to access the file, ouch!, suspect database. Next restart, file
weren't open by other process,
> SQL Server turned off the autoclose option.
> Autoclose is not designed for production databases!
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Jonathan Wareham" <JonathanW@.CooperParry.com> wrote in message
> news:OHdeeaBYEHA.644@.tk2msftngp13.phx.gbl...
> > Hi,
> >
> > Our network monitoring software reported the following message :
> >
> > The database "MSCRM" in the instance "MSSQLSERVER" is in a critical
state.
> > The state is: Suspect
> >
> > After looking at SQL Enterprise Manager, the database appears to be fine
and
> > I can browse tables, views, stored procedures and query the database as
> > normal. However when I looked at the SQL Server Error Log I found many
> > messages reporting 'Starting up database 'MSCRM'.
> >
> > Any ideas?
> >
> > Jonathan
> >
> > Here is a sample log from this morning :
> >
> >
> > 2004-07-02 09:29:53.76 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:54.48 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:59.17 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:59.43 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:59.67 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:29:59.93 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:00.24 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:00.48 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:00.82 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:01.06 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:01.46 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:01.74 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:02.03 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:30:02.32 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:32:19.81 spid89 Starting up database 'MSCRM'.
> > 2004-07-02 09:45:00.48 spid72 Starting up database 'MSCRM'.
> > 2004-07-02 09:45:01.06 spid72 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:00.23 spid91 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:00.65 spid91 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:00.89 spid101 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:01.60 spid101 Starting up database 'MSCRM'.
> > 2004-07-02 10:00:06.99 spid91 Starting up database 'MSCRM'.
> >
> >
>|||I just noticed a typo in my last post. I wrote:
" Next restart, file weren't open by other process, SQL Server turned off the autoclose option."
Should have been:
"...SQL Server turned off the suspect status."
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jonathan Wareham" <JonathanW@.CooperParry.com> wrote in message
news:%23R%23QHwBYEHA.2016@.TK2MSFTNGP11.phx.gbl...
> Many thanks Tibor!
> Jonathan
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23U0H0dBYEHA.3156@.TK2MSFTNGP12.phx.gbl...
> > Turn off autoclose for the database. What probably happened is that you
> have autoclose, some other
> > process (like anti-virus) got hold of the file while SQL Server didn't
> have it opened, SQL server
> > tried to access the file, ouch!, suspect database. Next restart, file
> weren't open by other process,
> > SQL Server turned off the autoclose option.
> >
> > Autoclose is not designed for production databases!
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Jonathan Wareham" <JonathanW@.CooperParry.com> wrote in message
> > news:OHdeeaBYEHA.644@.tk2msftngp13.phx.gbl...
> > > Hi,
> > >
> > > Our network monitoring software reported the following message :
> > >
> > > The database "MSCRM" in the instance "MSSQLSERVER" is in a critical
> state.
> > > The state is: Suspect
> > >
> > > After looking at SQL Enterprise Manager, the database appears to be fine
> and
> > > I can browse tables, views, stored procedures and query the database as
> > > normal. However when I looked at the SQL Server Error Log I found many
> > > messages reporting 'Starting up database 'MSCRM'.
> > >
> > > Any ideas?
> > >
> > > Jonathan
> > >
> > > Here is a sample log from this morning :
> > >
> > >
> > > 2004-07-02 09:29:53.76 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:54.48 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:59.17 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:59.43 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:59.67 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:29:59.93 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:00.24 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:00.48 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:00.82 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:01.06 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:01.46 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:01.74 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:02.03 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:30:02.32 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:32:19.81 spid89 Starting up database 'MSCRM'.
> > > 2004-07-02 09:45:00.48 spid72 Starting up database 'MSCRM'.
> > > 2004-07-02 09:45:01.06 spid72 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:00.23 spid91 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:00.65 spid91 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:00.89 spid101 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:01.60 spid101 Starting up database 'MSCRM'.
> > > 2004-07-02 10:00:06.99 spid91 Starting up database 'MSCRM'.
> > >
> > >
> >
> >
>