On Mar 30, 10:08 am, war_whee...@yahoo.com wrote:
> I created the db with the attached script and I am able to access it
> until I reboot the server. I've tried enabling flag 1807 via the SQL
> server service and the startup parameters of the instance. In all
> cases the database always come up suspect after a reboot. There was
> one instance where I was able to recover, but I am not sure how that
> happened.
>
> Does anyone have an idea of how I can reboot the server without the
> database becomming suspect?
>
> USE MASTER
> GO
> DBCC TRACEON(1807)
> GO
> --DBCC TRACEOFF(1807)
> --DBCC TRACESTATUS(1807)
> GO
> CREATE DATABASE ReadyNAS ON
> ( NAME = ReadyNAS_Data,
> FILENAME = '\\NAS1\NASDisk\SQL Server\ReadyNAS\ReadyNAS_Data.mdf',
> SIZE = 100MB,
> MAXSIZE = 20GB,
> FILEGROWTH = 20MB)
> LOG ON ( NAME = ReadyNAS_Log,
> FILENAME = '\\NAS1\NASDisk\SQL Server\ReadyNAS\ReadyNAS_Log.ldf',
> SIZE = 20MB,
> MAXSIZE = 100MB,
> FILEGROWTH = 10MB)

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

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

<mooregr_deletet...@greenms.com> wrote:
> <war_whee...@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

<war_wheelan@yahoo.com> wrote in message
news:1176903880.900635.102490@y80g2000hsf.googlegroups.com...
> On Apr 1, 10:01 am, "Greg D. Moore \(Strider\)"
> <mooregr_deletet...@greenms.com> wrote:
>> <war_whee...@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
>
>
> I tried setting the database to auto_close and also tried read_only
> which didn't correct the problem.

> What I mean is I still had to
> restart the service when the database was set to read_only, but I was
> able to access it. I also found that accessing the tables from the
> read_only database was quicker. On the other hand, when I set the
> database to auto_close I couldn't access it after a reboot even when
> restarting the service. The only was that I was able to access the
> database was to remove the auto_close options.
>