|
|
Posted by Mike on 12/21/07 12:02
On Dec 20, 10:15 pm, Erland Sommarskog <esq...@sommarskog.se> wrote:
> I am glad to see that you finally got the startup options working, Mike.
I've got even further now!
I used Management Studio to connect; but when you go in you mustn't
connect straight away as the object browser maintains a SQL connection
(no idea why it needs to). Then you can just open "Database Engine
Query" and bob's your uncle.
I've moved the msdb and model databases now, and successfully. But I
have a further problem.
I inadvertently moved tempdb and templog while the SQL service wasn't
running. I've now moved them back from whence they came, and SQL
starts fine with the -m;-c;-T3608 flags set. But when I take these
options out, SQL refuses to start with the following error in
ERRORLOG:
2007-12-21 11:49:38.88 Server Microsoft SQL Server 2005 -
9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-12-21 11:49:38.88 Server (c) 2005 Microsoft Corporation.
2007-12-21 11:49:38.88 Server All rights reserved.
2007-12-21 11:49:38.88 Server Server process ID is 4712.
2007-12-21 11:49:38.88 Server Authentication mode is MIXED.
2007-12-21 11:49:38.88 Server Logging SQL Server messages in file
'D:\MSSQL\LOG\ERRORLOG'.
2007-12-21 11:49:38.88 Server This instance of SQL Server last
reported using a process ID of 4512 at 21/12/2007 11:43:54 (local)
21/12/2007 11:43:54 (UTC). This is an informational message only; no
user action is required.
2007-12-21 11:49:38.88 Server Registry startup parameters:
2007-12-21 11:49:38.88 Server -d D:\MSSQL\DATA\master.mdf
2007-12-21 11:49:38.88 Server -e D:\MSSQL\LOG\ERRORLOG
2007-12-21 11:49:38.88 Server -l C:\MSSQL\Logs\mastlog.ldf
2007-12-21 11:49:38.88 Server SQL Server is starting at normal
priority base (=7). This is an informational message only. No user
action is required.
2007-12-21 11:49:38.88 Server Detected 8 CPUs. This is an
informational message; no user action is required.
2007-12-21 11:49:39.04 Server Set AWE Enabled to 1 in the
configuration parameters to allow use of more memory.
2007-12-21 11:49:39.28 Server Using dynamic lock allocation.
Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per
node. This is an informational message only. No user action is
required.
2007-12-21 11:49:39.29 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2007-12-21 11:49:40.32 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user
action is required.
2007-12-21 11:49:40.32 Server Database mirroring has been enabled
on this instance of SQL Server.
2007-12-21 11:49:40.32 spid5s Starting up database 'master'.
2007-12-21 11:49:40.34 spid5s SQL Trace ID 1 was started by login
"sa".
2007-12-21 11:49:40.34 spid5s Starting up database
'mssqlsystemresource'.
2007-12-21 11:49:40.34 spid5s The resource database build version
is 9.00.3042. This is an informational message only. No user action is
required.
2007-12-21 11:49:40.35 spid5s Server name is 'MYSERVER
\MYINSTANCE'. This is an informational message only. No user action is
required.
2007-12-21 11:49:40.35 spid9s Starting up database 'model'.
2007-12-21 11:49:40.37 spid9s Clearing tempdb database.
2007-12-21 11:49:40.37 spid9s Error: 913, Severity: 16, State: 8.
2007-12-21 11:49:40.37 spid9s Could not find database ID 2.
Database may not be activated yet or may be in transition. Reissue the
query once the database is available. If you do not think this error
is due to a database that is transitioning its state and this error
continues to occur, contact your primary support provider. Please have
available for review the Microsoft SQL Server error log and any
additional information relevant to the circumstances when the error
occurred.
2007-12-21 11:49:40.37 spid9s Could not create tempdb. You may
not have enough disk space available. Free additional disk space by
deleting other files on the tempdb drive and then restart SQL Server.
Check for additional errors in the event log that may indicate why the
tempdb files could not be initialized.
2007-12-21 11:49:40.37 spid9s SQL Trace was stopped due to server
shutdown. Trace ID = '1'. This is an informational message only; no
user action is required.
The event log contains the following entry:
"Could not find database ID 2. Database may not be activated yet or
may be in transition. Reissue the query once the database is
available. If you do not think this error is due to a database that is
transitioning its state and this error continues to occur, contact
your primary support provider. Please have available for review the
Microsoft SQL Server error log and any additional information relevant
to the circumstances when the error occurred.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."
I seem to be lurching from one obscure problem to another. I don't
want my database to be single-user!!
Thanks for the help so far, and thanks for any help in solving this
new conundrum.
Mike.
Navigation:
[Reply to this message]
|