Posted by war_wheelan on 03/31/07 14:16

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?

• Next in forum: Re: Newbie on permissions: ADO.NET, C++.NET, SQL SERVER 2005 EXPRESS, Visual Studio 2005
• Prev in forum: Re: how could I ???
• 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]