Posted by Erland Sommarskog on 03/31/07 21:49

(war_wheelan@yahoo.com) writes:
> I've figure out how to reboot the server and make the networked
> database accessible again. After the reboot, I need to manually
> restart the SQL Server service.
>
> Does anyone have an idea why I need to restart the service when I is
> configured to start automatically? Also is there a way to have this
> happen automatically via a script of something?

I would guess what happens is that the SQL Server service starts up
before the network connection has been established. Since the database
is not found at the point, it's marked suspect.

One thing you could try is to set the database to autoclose. I'm not sure
that it will actually work; maybe SQL Server still tries to access the
database on startup.

I don't know if it's possible to delay SQL Server starting up by making
it depending on the network service that makes network shares available.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: for jayne: highly comforting tunes - vomye eb - (1/1)
• Prev in forum: Re: Newbie on permissions: ADO.NET, C++.NET, SQL SERVER 2005 EXPRESS, Visual Studio 2005
• Thread view: Re: I have a database on a network drive that I use for archiving purposes, but when the server is rebooted the database becomes suspect.

[Reply to this message]