Posted by Greg D. Moore \(Strider\) on 04/01/07 14:01

<war_wheelan@yahoo.com> wrote in message
news:1175350571.321521.171840@b75g2000hsg.googlegroups.com...

> 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?
>

Yes, my guess is that SQL Server is starting BEFORE the workstation service
(I believe that's the one required) so that UNC shares are not available
until AFTER SQL Server starts.

Restarting SQL Server works because the drives are available at that point.

You can go into the properties of the SQL Server service and play around
with dependencies and that should allow you to fix it.



--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

• Next in forum: Re: The old inability to toggle/change/switch between ALTER PROCEDURE <---> CREATE PROCEDURE bug (or is it a feature?)
• Prev in forum: Re: SQL Datatypes
• 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]