Groups | Blog | Home
all groups > sql server new users > may 2006 >

sql server new users : Starting SQL 2000 Server SP4 in Single User Mode


Alexander
5/11/2006 10:24:49 AM
Hi Group,

I have the following problem: I am running the Enterprise Edition of SQL
Server 2000 SP4. I am trying to start the server in Single-User-Mode but it
isnt starting. Thats what I am getting:

2006-05-11 10:09:22.12 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2006-05-11 10:09:22.42 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-05-11 10:09:22.48 server All rights reserved.
2006-05-11 10:09:22.53 server Server Process ID is 1480.
2006-05-11 10:09:22.58 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-05-11 10:09:22.80 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-05-11 10:09:23.02 server SQL Server configured for thread mode
processing.
2006-05-11 10:09:23.14 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-05-11 10:09:23.24 server Attempting to initialize Distributed
Transaction Coordinator.
2006-05-11 10:09:24.58 spid3 Warning ******************
2006-05-11 10:09:24.63 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2006-05-11 10:09:24.72 spid3 Starting up database 'master'.
2006-05-11 10:09:25.14 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-05-11 10:09:25.31 server SQL server listening on 10.237.0.16: 1433.
2006-05-11 10:09:25.35 server SQL server listening on 127.0.0.1: 1433.
2006-05-11 10:09:25.65 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-05-11 10:09:25.86 server SQL Server is ready for client connections
2006-05-11 10:09:25.62 spid5 Starting up database 'model'.
2006-05-11 10:09:25.93 spid3 Server name is 'X'.
2006-05-11 10:09:26.04 spid7 Starting up database 'msdb'.
2006-05-11 10:09:26.12 spid8 Starting up database 'pubs'.
2006-05-11 10:09:26.20 spid9 Starting up database 'Northwind'.
2006-05-11 10:09:26.29 spid10 Starting up database 'ReportServer'.
2006-05-11 10:09:27.09 spid5 Clearing tempdb database.
2006-05-11 10:09:27.14 spid8 Starting up database 'ReportServerTempDB'.
2006-05-11 10:09:27.87 spid5 Starting up database 'tempdb'.
2006-05-11 10:09:28.06 spid3 Recovery complete.
2006-05-11 10:09:28.11 spid3 SQL global counter collection task is
created.

What could be a reason for this?

Thanks for your answers...



Steve Dybing [MSFT]
5/11/2006 12:01:55 PM
I don't see anything wrong here. Did you start it from a command prompt like
"sqlservr.exe -m" and are expecting control to be returned to the command
line? You won't see that c:\ prompt again until SQL Server is stopped.

--
Sincerely,
Steve Dybing

This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view]

AddThis Social Bookmark Button