Is using Enterprise Manage across the internet secure?

If I am using enterprise manager across the internet to access an SQL Server
, is it secure? Can I make database changes, passwords changes and view con
fidential table data securely. Or do I need to use another mechanism.Enterprise Manager is just an application, it sounds like you are worried
about the data transferred over the wire. If so, you should look into SSL
encryption.
276553 HOW TO: Enable SSL Encryption for SQL Server 2000 with Certificate
Server http://support.microsoft.com/?id=276553
316898 HOW TO: Enable SSL Encryption for SQL Server 2000 with Microsoft...
http://support.microsoft.com/?id=316898
324777 WebCast: Microsoft SQL Server 2000: How to Configure SSL Encryption
http://support.microsoft.com/?id=324777
318605 INF: How SQL Server Uses a Certificate When the Force Protocol
http://support.microsoft.com/?id=318605
325757 INF: Using SQL Server 2000 with FIPS 140-1 Ciphers
http://support.microsoft.com/?id=325757
302409 FIX: Unable to Connect to SQL Server 2000 When Certificate
Authority... http://support.microsoft.com/?id=302409
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Is this indication of Deadlock Occurs?

Hi All,
I see the following in the SQL (error) log and am curious as to
why it shows up (repeatedly). Server OS is Windows 2003 Enterprise,
SQL Server 2000 SP4. This server uses the Intel with 4 processors.
2005-11-13 12:52:01.71 spid4 Victim Resource Owner:
2005-11-13 12:52:01.71 spid4 ResType:ExchangeId Stype:'AND' SPID:93
ECID:33
Ec0xA9CA60C0) Value:0x802d1c0c
Cost0/270F)
2005-11-13 12:52:06.71 spid4 Victim Resource Owner:
2005-11-13 12:52:06.71 spid4 ... (similar as above)
2005-11-13 12:52:11.71 spid4 Victim Resource Owner:
2005-11-13 12:52:11.71 spid4 ... (similar as above)
2005-11-13 12:52:16.71 spid4 Victim Resource Owner:
2005-11-13 12:52:16.71 spid4 ... (similar as above)
As you can see, it happens every 5 seconds, and somehow
stop by itself. I also realize that before the shows that,
I do enable DBCC TRACEON (3605,1204,-1).
The questions is:
1. does it normal situation?
2. does it means that locking occurs, but no deadlock occurs?
3. or does it means that locking occurs, and deadlock happens,
and Lock Manager does terminate one/more SPID?
4. what is 'ResType:ExchangeId'?
Really need your help.
Regards,
Johan
Looks like deadlock did you look through the profile who the culprit
SQL is
Regards ,
C#, VB.NET , SQL SERVER , UML , DESIGN Patterns Interview question book
http://www.geocities.com/dotnetinterviews/
My Interview Blog
http://spaces.msn.com/members/dotnetinterviews/
|||If you run sp_who2 while this is going on you will see the spid that is
blocking your transaction.
You can then run dbcc inputbuffer (spid #) to get more insight.
burt_king@.yahoo.com
"Johan" wrote:

> Hi All,
> I see the following in the SQL (error) log and am curious as to
> why it shows up (repeatedly). Server OS is Windows 2003 Enterprise,
> SQL Server 2000 SP4. This server uses the Intel with 4 processors.
> 2005-11-13 12:52:01.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:01.71 spid4 ResType:ExchangeId Stype:'AND' SPID:93
> ECID:33
> Ec0xA9CA60C0) Value:0x802d1c0c
> Cost0/270F)
> 2005-11-13 12:52:06.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:06.71 spid4 ... (similar as above)
> 2005-11-13 12:52:11.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:11.71 spid4 ... (similar as above)
> 2005-11-13 12:52:16.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:16.71 spid4 ... (similar as above)
> As you can see, it happens every 5 seconds, and somehow
> stop by itself. I also realize that before the shows that,
> I do enable DBCC TRACEON (3605,1204,-1).
> The questions is:
> 1. does it normal situation?
> 2. does it means that locking occurs, but no deadlock occurs?
> 3. or does it means that locking occurs, and deadlock happens,
> and Lock Manager does terminate one/more SPID?
> 4. what is 'ResType:ExchangeId'?
> Really need your help.
> Regards,
> Johan
>
>
|||Since it happened sporadically and quite fast so I don't have the chance to
run SQL Profiler.
BTW, if I have the chance to run SQL Profiler, what 'Event Classes' to
capture the trace?
Thanks
"shiv_koirala@.yahoo.com" wrote:

> Looks like deadlock did you look through the profile who the culprit
> SQL is
> --
> Regards ,
> C#, VB.NET , SQL SERVER , UML , DESIGN Patterns Interview question book
> http://www.geocities.com/dotnetinterviews/
> My Interview Blog
> http://spaces.msn.com/members/dotnetinterviews/
>
|||Since it happened sporadically and quite fast so I don't have the chance to
run sp_who2.
I also do some searching, that if deadlock really occured, then this message
will show up in ERRORLOG
Your transaction (process ID #52) was deadlocked on {lock | communication
buffer | thread} resources with another process and has been chosen as the
deadlock victim. Rerun your transaction.
Basically I need some confirmation, LOG entry below:
ResType:ExchangeId Stype:'AND' SPID:93 ECID:33 Ec0xA9CA60C0)
Value:0x802d1c0c
1. does it means that locking occurs, but no deadlock occurs?
2. if it happened quite frequently, will it degrade the overall DB
performance?
Thanks,
Johan
"burt_king" wrote:

> If you run sp_who2 while this is going on you will see the spid that is
> blocking your transaction.
> You can then run dbcc inputbuffer (spid #) to get more insight.
>
> --
> burt_king@.yahoo.com
>
sql

Is this indication of Deadlock Occurs?

Hi All,
I see the following in the SQL (error) log and am curious as to
why it shows up (repeatedly). Server OS is Windows 2003 Enterprise,
SQL Server 2000 SP4. This server uses the Intel with 4 processors.
2005-11-13 12:52:01.71 spid4 Victim Resource Owner:
2005-11-13 12:52:01.71 spid4 ResType:ExchangeId Stype:'AND' SPID:93
ECID:33
Ec:(0xA9CA60C0) Value:0x802d1c0c
Cost:(0/270F)
2005-11-13 12:52:06.71 spid4 Victim Resource Owner:
2005-11-13 12:52:06.71 spid4 ... (similar as above)
2005-11-13 12:52:11.71 spid4 Victim Resource Owner:
2005-11-13 12:52:11.71 spid4 ... (similar as above)
2005-11-13 12:52:16.71 spid4 Victim Resource Owner:
2005-11-13 12:52:16.71 spid4 ... (similar as above)
As you can see, it happens every 5 seconds, and somehow
stop by itself. I also realize that before the shows that,
I do enable DBCC TRACEON (3605,1204,-1).
The questions is:
1. does it normal situation?
2. does it means that locking occurs, but no deadlock occurs?
3. or does it means that locking occurs, and deadlock happens,
and Lock Manager does terminate one/more SPID?
4. what is 'ResType:ExchangeId'?
Really need your help.
Regards,
JohanLooks like deadlock did you look through the profile who the culprit
SQL is
--
Regards ,
C#, VB.NET , SQL SERVER , UML , DESIGN Patterns Interview question book
http://www.geocities.com/dotnetinterviews/
My Interview Blog
http://spaces.msn.com/members/dotnetinterviews/|||If you run sp_who2 while this is going on you will see the spid that is
blocking your transaction.
You can then run dbcc inputbuffer (spid #) to get more insight.
burt_king@.yahoo.com
"Johan" wrote:
> Hi All,
> I see the following in the SQL (error) log and am curious as to
> why it shows up (repeatedly). Server OS is Windows 2003 Enterprise,
> SQL Server 2000 SP4. This server uses the Intel with 4 processors.
> 2005-11-13 12:52:01.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:01.71 spid4 ResType:ExchangeId Stype:'AND' SPID:93
> ECID:33
> Ec:(0xA9CA60C0) Value:0x802d1c0c
> Cost:(0/270F)
> 2005-11-13 12:52:06.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:06.71 spid4 ... (similar as above)
> 2005-11-13 12:52:11.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:11.71 spid4 ... (similar as above)
> 2005-11-13 12:52:16.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:16.71 spid4 ... (similar as above)
> As you can see, it happens every 5 seconds, and somehow
> stop by itself. I also realize that before the shows that,
> I do enable DBCC TRACEON (3605,1204,-1).
> The questions is:
> 1. does it normal situation?
> 2. does it means that locking occurs, but no deadlock occurs?
> 3. or does it means that locking occurs, and deadlock happens,
> and Lock Manager does terminate one/more SPID?
> 4. what is 'ResType:ExchangeId'?
> Really need your help.
> Regards,
> Johan
>
>|||Since it happened sporadically and quite fast so I don't have the chance to
run SQL Profiler.
BTW, if I have the chance to run SQL Profiler, what 'Event Classes' to
capture the trace?
Thanks
"shiv_koirala@.yahoo.com" wrote:
> Looks like deadlock did you look through the profile who the culprit
> SQL is
> --
> Regards ,
> C#, VB.NET , SQL SERVER , UML , DESIGN Patterns Interview question book
> http://www.geocities.com/dotnetinterviews/
> My Interview Blog
> http://spaces.msn.com/members/dotnetinterviews/
>|||Since it happened sporadically and quite fast so I don't have the chance to
run sp_who2.
I also do some searching, that if deadlock really occured, then this message
will show up in ERRORLOG
--
Your transaction (process ID #52) was deadlocked on {lock | communication
buffer | thread} resources with another process and has been chosen as the
deadlock victim. Rerun your transaction.
--
Basically I need some confirmation, LOG entry below:
--
ResType:ExchangeId Stype:'AND' SPID:93 ECID:33 Ec:(0xA9CA60C0)
Value:0x802d1c0c
--
1. does it means that locking occurs, but no deadlock occurs?
2. if it happened quite frequently, will it degrade the overall DB
performance?
Thanks,
Johan
"burt_king" wrote:
> If you run sp_who2 while this is going on you will see the spid that is
> blocking your transaction.
> You can then run dbcc inputbuffer (spid #) to get more insight.
>
> --
> burt_king@.yahoo.com
>

Is this indication of Deadlock Occurs?

Hi All,
I see the following in the SQL (error) log and am curious as to
why it shows up (repeatedly). Server OS is Windows 2003 Enterprise,
SQL Server 2000 SP4. This server uses the Intel with 4 processors.
2005-11-13 12:52:01.71 spid4 Victim Resource Owner:
2005-11-13 12:52:01.71 spid4 ResType:ExchangeId Stype:'AND' SPID:93
ECID:33
Ec0xA9CA60C0) Value:0x802d1c0c
Cost0/270F)
2005-11-13 12:52:06.71 spid4 Victim Resource Owner:
2005-11-13 12:52:06.71 spid4 ... (similar as above)
2005-11-13 12:52:11.71 spid4 Victim Resource Owner:
2005-11-13 12:52:11.71 spid4 ... (similar as above)
2005-11-13 12:52:16.71 spid4 Victim Resource Owner:
2005-11-13 12:52:16.71 spid4 ... (similar as above)
As you can see, it happens every 5 seconds, and somehow
stop by itself. I also realize that before the shows that,
I do enable DBCC TRACEON (3605,1204,-1).
The questions is:
1. does it normal situation?
2. does it means that locking occurs, but no deadlock occurs?
3. or does it means that locking occurs, and deadlock happens,
and Lock Manager does terminate one/more SPID?
4. what is 'ResType:ExchangeId'?
Really need your help.
Regards,
JohanLooks like deadlock did you look through the profile who the culprit
SQL is
Regards ,
C#, VB.NET , SQL SERVER , UML , DESIGN Patterns Interview question book
http://www.geocities.com/dotnetinterviews/
My Interview Blog
http://spaces.msn.com/members/dotnetinterviews/|||If you run sp_who2 while this is going on you will see the spid that is
blocking your transaction.
You can then run dbcc inputbuffer (spid #) to get more insight.
burt_king@.yahoo.com
"Johan" wrote:

> Hi All,
> I see the following in the SQL (error) log and am curious as to
> why it shows up (repeatedly). Server OS is Windows 2003 Enterprise,
> SQL Server 2000 SP4. This server uses the Intel with 4 processors.
> 2005-11-13 12:52:01.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:01.71 spid4 ResType:ExchangeId Stype:'AND' SPID:93
> ECID:33
> Ec0xA9CA60C0) Value:0x802d1c0c
> Cost0/270F)
> 2005-11-13 12:52:06.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:06.71 spid4 ... (similar as above)
> 2005-11-13 12:52:11.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:11.71 spid4 ... (similar as above)
> 2005-11-13 12:52:16.71 spid4 Victim Resource Owner:
> 2005-11-13 12:52:16.71 spid4 ... (similar as above)
> As you can see, it happens every 5 seconds, and somehow
> stop by itself. I also realize that before the shows that,
> I do enable DBCC TRACEON (3605,1204,-1).
> The questions is:
> 1. does it normal situation?
> 2. does it means that locking occurs, but no deadlock occurs?
> 3. or does it means that locking occurs, and deadlock happens,
> and Lock Manager does terminate one/more SPID?
> 4. what is 'ResType:ExchangeId'?
> Really need your help.
> Regards,
> Johan
>
>|||Since it happened sporadically and quite fast so I don't have the chance to
run SQL Profiler.
BTW, if I have the chance to run SQL Profiler, what 'Event Classes' to
capture the trace?
Thanks
"shiv_koirala@.yahoo.com" wrote:

> Looks like deadlock did you look through the profile who the culprit
> SQL is
> --
> Regards ,
> C#, VB.NET , SQL SERVER , UML , DESIGN Patterns Interview question book
> http://www.geocities.com/dotnetinterviews/
> My Interview Blog
> http://spaces.msn.com/members/dotnetinterviews/
>|||Since it happened sporadically and quite fast so I don't have the chance to
run sp_who2.
I also do some searching, that if deadlock really occured, then this message
will show up in ERRORLOG
--
Your transaction (process ID #52) was deadlocked on {lock | communicati
on
buffer | thread} resources with another process and has been chosen as the
deadlock victim. Rerun your transaction.
--
Basically I need some confirmation, LOG entry below:
--
ResType:ExchangeId Stype:'AND' SPID:93 ECID:33 Ec0xA9CA60C0)
Value:0x802d1c0c
--
1. does it means that locking occurs, but no deadlock occurs?
2. if it happened quite frequently, will it degrade the overall DB
performance?
Thanks,
Johan
"burt_king" wrote:

> If you run sp_who2 while this is going on you will see the spid that is
> blocking your transaction.
> You can then run dbcc inputbuffer (spid #) to get more insight.
>
> --
> burt_king@.yahoo.com
>

is this a connection problem or am I going bonkers?

I have SQL installed locally, and it has been working fine for some time.
However, today when I went to Enterprise Manager I could see the tree view
but as soon as I selected "Databases" everything froze, Task Manager
reported that the application was not responding. I left it for 10 minutes
and the
screen stayed stuck with the hourglass.
I tried re-starting the SQL service and rebooting the box, but the same
problem occured.
When I try and use Query Analyser, I cannot select a database from the
drop down list, but, I can use the "Use" command to choose a database and I
can
run a query. It is unblievably slow though.
Just tried to create a new ODBC connection and the test failed because of a
timeout.
Does anyone have any clues?
I've posted the log below
thanks
J
2004-11-30 14:59:48.59 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2004-11-30 14:59:48.60 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-11-30 14:59:48.60 server All rights reserved.
2004-11-30 14:59:48.60 server Server Process ID is 1636.
2004-11-30 14:59:48.60 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2004-11-30 14:59:48.66 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-11-30 14:59:49.44 server SQL Server configured for thread mode
processing.
2004-11-30 14:59:49.49 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2004-11-30 14:59:49.55 server Attempting to initialize Distributed
Transaction Coordinator.
2004-11-30 14:59:49.96 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2004-11-30 14:59:50.01 spid3 Starting up database 'master'.
2004-11-30 14:59:52.47 spid3 0 transactions rolled back in database
'master' (1).
2004-11-30 14:59:52.48 spid3 Recovery is checkpointing database 'master'
(1)
2004-11-30 14:59:52.62 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-11-30 14:59:52.63 spid5 Starting up database 'model'.
2004-11-30 14:59:52.76 spid3 Server name is 'OBIWAN'.
2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 7
2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 11
2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 12
2004-11-30 14:59:52.78 server SQL server listening on Shared Memory,
Named Pipes.
2004-11-30 14:59:52.78 server SQL Server is ready for client connections
2004-11-30 14:59:52.78 spid8 Starting up database 'msdb'.
2004-11-30 14:59:52.85 spid9 Starting up database 'pubs'.
2004-11-30 14:59:52.86 spid10 Starting up database 'Northwind'.
2004-11-30 14:59:52.99 spid11 Starting up database 'isoglobal'.
2004-11-30 14:59:53.80 spid5 Clearing tempdb database.
2004-11-30 14:59:54.18 spid9 Starting up database 'vmserver'.
2004-11-30 14:59:54.33 spid10 Starting up database 'vmserver_delivery'.
2004-11-30 14:59:56.76 spid5 Starting up database 'tempdb'.
2004-11-30 14:59:57.02 spid3 Recovery complete.
2004-11-30 15:35:06.94 spid52 Starting up database '3663'.
2004-11-30 15:35:07.47 spid52 Starting up database 'demo'.
2004-11-30 15:35:07.81 spid52 Starting up database 'fsspda'.
2004-11-30 15:35:10.27 spid51 Starting up database '3663'.
2004-11-30 15:35:26.30 spid51 Starting up database 'demo'.
2004-11-30 15:35:45.90 spid51 Starting up database 'fsspda'.
2004-11-30 15:36:09.88 spid51 Starting up database '3663'.
2004-11-30 15:36:27.73 spid51 Starting up database 'demo'.
2004-11-30 15:36:45.81 spid51 Starting up database 'fsspda'.
2004-11-30 15:37:24.86 spid51 Starting up database 'demo'.
2004-11-30 15:37:43.23 spid51 Starting up database 'demo'.
2004-11-30 15:38:03.14 spid51 Starting up database 'demo'.
2004-11-30 15:50:39.57 spid53 Using 'xpstar.dll' version '2000.80.194' to
execute extended stored procedure 'sp_MSgetversion'.
2004-11-30 15:50:56.32 spid53 Starting up database '3663'.
2004-11-30 15:50:56.79 spid53 Starting up database 'fsspda'.
2004-11-30 15:50:57.26 spid53 Starting up database '3663'.
2004-11-30 15:51:13.34 spid53 Starting up database 'fsspda'.
2004-11-30 15:51:27.99 spid53 Starting up database '3663'.
2004-11-30 15:51:43.49 spid53 Starting up database 'fsspda'.
2004-11-30 15:51:59.48 spid53 Starting up database '3663'.
2004-11-30 15:52:22.68 spid53 Starting up database 'fsspda'.
2004-11-30 15:52:40.95 spid53 Starting up database '3663'.
2004-11-30 15:53:01.00 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:16.65 spid53 Starting up database '3663'.
2004-11-30 15:53:33.17 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:48.53 spid53 Starting up database '3663'.
2004-11-30 15:53:49.39 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:50.02 spid53 Starting up database '3663'.
2004-11-30 15:53:50.78 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:51.56 spid53 Starting up database '3663'.
2004-11-30 15:53:52.22 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:52.53 spid53 Starting up database '3663'.
2004-11-30 15:53:52.87 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:53.16 spid53 Starting up database '3663'.
2004-11-30 15:53:53.52 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:53.87 spid53 Starting up database '3663'.
2004-11-30 15:53:54.19 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:54.49 spid53 Starting up database '3663'.
2004-11-30 15:53:54.97 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:55.33 spid53 Starting up database '3663'.
2004-11-30 15:53:55.68 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:56.01 spid53 Starting up database '3663'.
2004-11-30 15:53:56.90 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:57.45 spid53 Starting up database '3663'.
2004-11-30 15:53:57.81 spid53 Starting up database 'fsspda'.
2004-11-30 15:54:04.61 spid51 Starting up database 'fsspda'.
2004-11-30 15:54:05.02 spid51 Starting up database 'fsspda'.
2004-11-30 15:54:05.45 spid51 Starting up database 'fsspda'.
2004-11-30 15:54:09.62 spid51 Starting up database '3663'.
2004-11-30 15:54:10.05 spid51 Starting up database 'demo'.
2004-11-30 15:54:17.14 spid51 Starting up database 'demo'.
2004-11-30 15:54:17.46 spid51 Starting up database 'demo'.
2004-11-30 15:54:17.82 spid51 Starting up database 'demo'.
2004-11-30 15:54:33.58 spid53 Starting up database 'Route'.
2004-11-30 15:54:34.32 spid53 Starting up database '3663'.
2004-11-30 15:54:34.76 spid53 Starting up database 'fsspda'.
2004-11-30 15:54:35.07 spid53 Starting up database '3663'.
2004-11-30 15:54:35.38 spid53 Starting up database 'fsspda'.
2004-11-30 15:58:19.63 spid51 Starting up database '3663'.
2004-11-30 15:58:37.12 spid51 Starting up database 'fsspda'.
2004-11-30 15:58:52.46 spid51 Starting up database '3663'.
2004-11-30 15:59:09.98 spid51 Starting up database 'demo'.
2004-11-30 15:59:41.81 spid51 Starting up database 'fsspda'.
2004-11-30 15:59:59.34 spid51 Starting up database '3663'.
2004-11-30 16:00:15.76 spid51 Starting up database 'demo'.
2004-11-30 16:00:50.61 spid51 Starting up database 'fsspda'.
2004-11-30 16:00:51.36 spid51 Starting up database '3663'.
2004-11-30 16:01:10.96 spid51 Starting up database 'demo'.
2004-11-30 16:01:30.14 spid51 Starting up database 'fsspda'.
2004-11-30 16:01:45.79 spid51 Starting up database '3663'.
2004-11-30 16:02:01.59 spid51 Starting up database 'demo'.
2004-11-30 16:02:05.37 spid51 Starting up database 'fsspda'.
2004-11-30 16:02:21.41 spid51 Starting up database '3663'.
2004-11-30 16:02:38.84 spid51 Starting up database 'demo'.
2004-11-30 16:02:58.05 spid51 Starting up database 'fsspda'.
2004-11-30 16:03:13.71 spid51 Starting up database '3663'.
2004-11-30 16:03:34.68 spid51 Starting up database 'demo'.
2004-11-30 16:03:56.00 spid51 Starting up database 'fsspda'.
2004-11-30 16:04:12.85 spid51 Starting up database '3663'.
2004-11-30 16:04:29.93 spid51 Starting up database 'demo'.
2004-11-30 16:04:50.03 spid51 Starting up database 'fsspda'.
2004-11-30 16:05:06.56 spid51 Starting up database '3663'.
2004-11-30 16:05:24.32 spid51 Starting up database 'demo'.
2004-11-30 16:05:51.91 spid53 Starting up database '3663'.
2004-11-30 16:06:10.79 spid51 Starting up database 'fsspda'.
2004-11-30 16:06:26.38 spid53 Starting up database 'demo'.
2004-11-30 16:06:46.93 spid51 Starting up database '3663'.
2004-11-30 16:07:05.64 spid53 Starting up database 'fsspda'.
2004-11-30 16:07:21.08 spid51 Starting up database 'demo'.
2004-11-30 16:07:22.29 spid51 Starting up database 'fsspda'.
2004-11-30 16:07:40.60 spid51 Starting up database '3663'.
2004-11-30 16:07:59.85 spid51 Starting up database 'demo'.
2004-11-30 16:08:25.22 spid51 Starting up database 'fsspda'.
2004-11-30 16:08:44.40 spid51 Starting up database '3663'.
2004-11-30 16:09:02.97 spid51 Starting up database 'demo'.
2004-11-30 16:09:34.28 spid51 Starting up database 'fsspda'.
2004-11-30 16:12:52.66 spid51 Starting up database 'fsspda'.
2004-11-30 16:12:53.04 spid51 Starting up database 'demo'.
2004-11-30 16:12:53.45 spid51 Starting up database '3663'.
2004-11-30 16:12:56.66 spid52 Starting up database 'fsspda'.
Neither...it's from having auto close turned on. See my
posts to your same question in the server newsgroup.
-Sue
On Tue, 30 Nov 2004 09:45:07 -0800, "McFly"
<McFly@.discussions.microsoft.com> wrote:

> I have SQL installed locally, and it has been working fine for some time.
> However, today when I went to Enterprise Manager I could see the tree view
> but as soon as I selected "Databases" everything froze, Task Manager
> reported that the application was not responding. I left it for 10 minutes
>and the
> screen stayed stuck with the hourglass.
> I tried re-starting the SQL service and rebooting the box, but the same
> problem occured.
> When I try and use Query Analyser, I cannot select a database from the
> drop down list, but, I can use the "Use" command to choose a database and I
>can
> run a query. It is unblievably slow though.
>Just tried to create a new ODBC connection and the test failed because of a
>timeout.
>
> Does anyone have any clues?
>I've posted the log below
>thanks
>J
>2004-11-30 14:59:48.59 server Microsoft SQL Server 2000 - 8.00.194
>(Intel X86)
>Aug 6 2000 00:57:48
>Copyright (c) 1988-2000 Microsoft Corporation
>Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
>2004-11-30 14:59:48.60 server Copyright (C) 1988-2000 Microsoft
>Corporation.
>2004-11-30 14:59:48.60 server All rights reserved.
>2004-11-30 14:59:48.60 server Server Process ID is 1636.
>2004-11-30 14:59:48.60 server Logging SQL Server messages in file
>'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>2004-11-30 14:59:48.66 server SQL Server is starting at priority class
>'normal'(1 CPU detected).
>2004-11-30 14:59:49.44 server SQL Server configured for thread mode
>processing.
>2004-11-30 14:59:49.49 server Using dynamic lock allocation. [2500] Lock
>Blocks, [5000] Lock Owner Blocks.
>2004-11-30 14:59:49.55 server Attempting to initialize Distributed
>Transaction Coordinator.
>2004-11-30 14:59:49.96 server Failed to obtain
>TransactionDispenserInterface: Result Code = 0x8004d01b
>2004-11-30 14:59:50.01 spid3 Starting up database 'master'.
>2004-11-30 14:59:52.47 spid3 0 transactions rolled back in database
>'master' (1).
>2004-11-30 14:59:52.48 spid3 Recovery is checkpointing database 'master'
>(1)
>2004-11-30 14:59:52.62 server Using 'SSNETLIB.DLL' version '8.0.194'.
>2004-11-30 14:59:52.63 spid5 Starting up database 'model'.
>2004-11-30 14:59:52.76 spid3 Server name is 'OBIWAN'.
>2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 7
>2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 11
>2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 12
>2004-11-30 14:59:52.78 server SQL server listening on Shared Memory,
>Named Pipes.
>2004-11-30 14:59:52.78 server SQL Server is ready for client connections
>2004-11-30 14:59:52.78 spid8 Starting up database 'msdb'.
>2004-11-30 14:59:52.85 spid9 Starting up database 'pubs'.
>2004-11-30 14:59:52.86 spid10 Starting up database 'Northwind'.
>2004-11-30 14:59:52.99 spid11 Starting up database 'isoglobal'.
>2004-11-30 14:59:53.80 spid5 Clearing tempdb database.
>2004-11-30 14:59:54.18 spid9 Starting up database 'vmserver'.
>2004-11-30 14:59:54.33 spid10 Starting up database 'vmserver_delivery'.
>2004-11-30 14:59:56.76 spid5 Starting up database 'tempdb'.
>2004-11-30 14:59:57.02 spid3 Recovery complete.
>2004-11-30 15:35:06.94 spid52 Starting up database '3663'.
>2004-11-30 15:35:07.47 spid52 Starting up database 'demo'.
>2004-11-30 15:35:07.81 spid52 Starting up database 'fsspda'.
>2004-11-30 15:35:10.27 spid51 Starting up database '3663'.
>2004-11-30 15:35:26.30 spid51 Starting up database 'demo'.
>2004-11-30 15:35:45.90 spid51 Starting up database 'fsspda'.
>2004-11-30 15:36:09.88 spid51 Starting up database '3663'.
>2004-11-30 15:36:27.73 spid51 Starting up database 'demo'.
>2004-11-30 15:36:45.81 spid51 Starting up database 'fsspda'.
>2004-11-30 15:37:24.86 spid51 Starting up database 'demo'.
>2004-11-30 15:37:43.23 spid51 Starting up database 'demo'.
>2004-11-30 15:38:03.14 spid51 Starting up database 'demo'.
>2004-11-30 15:50:39.57 spid53 Using 'xpstar.dll' version '2000.80.194' to
>execute extended stored procedure 'sp_MSgetversion'.
>2004-11-30 15:50:56.32 spid53 Starting up database '3663'.
>2004-11-30 15:50:56.79 spid53 Starting up database 'fsspda'.
>2004-11-30 15:50:57.26 spid53 Starting up database '3663'.
>2004-11-30 15:51:13.34 spid53 Starting up database 'fsspda'.
>2004-11-30 15:51:27.99 spid53 Starting up database '3663'.
>2004-11-30 15:51:43.49 spid53 Starting up database 'fsspda'.
>2004-11-30 15:51:59.48 spid53 Starting up database '3663'.
>2004-11-30 15:52:22.68 spid53 Starting up database 'fsspda'.
>2004-11-30 15:52:40.95 spid53 Starting up database '3663'.
>2004-11-30 15:53:01.00 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:16.65 spid53 Starting up database '3663'.
>2004-11-30 15:53:33.17 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:48.53 spid53 Starting up database '3663'.
>2004-11-30 15:53:49.39 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:50.02 spid53 Starting up database '3663'.
>2004-11-30 15:53:50.78 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:51.56 spid53 Starting up database '3663'.
>2004-11-30 15:53:52.22 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:52.53 spid53 Starting up database '3663'.
>2004-11-30 15:53:52.87 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:53.16 spid53 Starting up database '3663'.
>2004-11-30 15:53:53.52 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:53.87 spid53 Starting up database '3663'.
>2004-11-30 15:53:54.19 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:54.49 spid53 Starting up database '3663'.
>2004-11-30 15:53:54.97 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:55.33 spid53 Starting up database '3663'.
>2004-11-30 15:53:55.68 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:56.01 spid53 Starting up database '3663'.
>2004-11-30 15:53:56.90 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:57.45 spid53 Starting up database '3663'.
>2004-11-30 15:53:57.81 spid53 Starting up database 'fsspda'.
>2004-11-30 15:54:04.61 spid51 Starting up database 'fsspda'.
>2004-11-30 15:54:05.02 spid51 Starting up database 'fsspda'.
>2004-11-30 15:54:05.45 spid51 Starting up database 'fsspda'.
>2004-11-30 15:54:09.62 spid51 Starting up database '3663'.
>2004-11-30 15:54:10.05 spid51 Starting up database 'demo'.
>2004-11-30 15:54:17.14 spid51 Starting up database 'demo'.
>2004-11-30 15:54:17.46 spid51 Starting up database 'demo'.
>2004-11-30 15:54:17.82 spid51 Starting up database 'demo'.
>2004-11-30 15:54:33.58 spid53 Starting up database 'Route'.
>2004-11-30 15:54:34.32 spid53 Starting up database '3663'.
>2004-11-30 15:54:34.76 spid53 Starting up database 'fsspda'.
>2004-11-30 15:54:35.07 spid53 Starting up database '3663'.
>2004-11-30 15:54:35.38 spid53 Starting up database 'fsspda'.
>2004-11-30 15:58:19.63 spid51 Starting up database '3663'.
>2004-11-30 15:58:37.12 spid51 Starting up database 'fsspda'.
>2004-11-30 15:58:52.46 spid51 Starting up database '3663'.
>2004-11-30 15:59:09.98 spid51 Starting up database 'demo'.
>2004-11-30 15:59:41.81 spid51 Starting up database 'fsspda'.
>2004-11-30 15:59:59.34 spid51 Starting up database '3663'.
>2004-11-30 16:00:15.76 spid51 Starting up database 'demo'.
>2004-11-30 16:00:50.61 spid51 Starting up database 'fsspda'.
>2004-11-30 16:00:51.36 spid51 Starting up database '3663'.
>2004-11-30 16:01:10.96 spid51 Starting up database 'demo'.
>2004-11-30 16:01:30.14 spid51 Starting up database 'fsspda'.
>2004-11-30 16:01:45.79 spid51 Starting up database '3663'.
>2004-11-30 16:02:01.59 spid51 Starting up database 'demo'.
>2004-11-30 16:02:05.37 spid51 Starting up database 'fsspda'.
>2004-11-30 16:02:21.41 spid51 Starting up database '3663'.
>2004-11-30 16:02:38.84 spid51 Starting up database 'demo'.
>2004-11-30 16:02:58.05 spid51 Starting up database 'fsspda'.
>2004-11-30 16:03:13.71 spid51 Starting up database '3663'.
>2004-11-30 16:03:34.68 spid51 Starting up database 'demo'.
>2004-11-30 16:03:56.00 spid51 Starting up database 'fsspda'.
>2004-11-30 16:04:12.85 spid51 Starting up database '3663'.
>2004-11-30 16:04:29.93 spid51 Starting up database 'demo'.
>2004-11-30 16:04:50.03 spid51 Starting up database 'fsspda'.
>2004-11-30 16:05:06.56 spid51 Starting up database '3663'.
>2004-11-30 16:05:24.32 spid51 Starting up database 'demo'.
>2004-11-30 16:05:51.91 spid53 Starting up database '3663'.
>2004-11-30 16:06:10.79 spid51 Starting up database 'fsspda'.
>2004-11-30 16:06:26.38 spid53 Starting up database 'demo'.
>2004-11-30 16:06:46.93 spid51 Starting up database '3663'.
>2004-11-30 16:07:05.64 spid53 Starting up database 'fsspda'.
>2004-11-30 16:07:21.08 spid51 Starting up database 'demo'.
>2004-11-30 16:07:22.29 spid51 Starting up database 'fsspda'.
>2004-11-30 16:07:40.60 spid51 Starting up database '3663'.
>2004-11-30 16:07:59.85 spid51 Starting up database 'demo'.
>2004-11-30 16:08:25.22 spid51 Starting up database 'fsspda'.
>2004-11-30 16:08:44.40 spid51 Starting up database '3663'.
>2004-11-30 16:09:02.97 spid51 Starting up database 'demo'.
>2004-11-30 16:09:34.28 spid51 Starting up database 'fsspda'.
>2004-11-30 16:12:52.66 spid51 Starting up database 'fsspda'.
>2004-11-30 16:12:53.04 spid51 Starting up database 'demo'.
>2004-11-30 16:12:53.45 spid51 Starting up database '3663'.
>2004-11-30 16:12:56.66 spid52 Starting up database 'fsspda'.
>

is this a connection problem or am I going bonkers?

I have SQL installed locally, and it has been working fine for some time.
However, today when I went to Enterprise Manager I could see the tree view
but as soon as I selected "Databases" everything froze, Task Manager
reported that the application was not responding. I left it for 10 minutes
and the
screen stayed stuck with the hourglass.
I tried re-starting the SQL service and rebooting the box, but the same
problem occured.
When I try and use Query Analyser, I cannot select a database from the
drop down list, but, I can use the "Use" command to choose a database and I
can
run a query. It is unblievably slow though.
Just tried to create a new ODBC connection and the test failed because of a
timeout.
Does anyone have any clues?
I've posted the log below
thanks
J
2004-11-30 14:59:48.59 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2004-11-30 14:59:48.60 server Copyright (C) 1988-2000 Microsoft
Corporation.
2004-11-30 14:59:48.60 server All rights reserved.
2004-11-30 14:59:48.60 server Server Process ID is 1636.
2004-11-30 14:59:48.60 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2004-11-30 14:59:48.66 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-11-30 14:59:49.44 server SQL Server configured for thread mode
processing.
2004-11-30 14:59:49.49 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2004-11-30 14:59:49.55 server Attempting to initialize Distributed
Transaction Coordinator.
2004-11-30 14:59:49.96 server Failed to obtain
TransactionDispenserInterface: Result Code = 0x8004d01b
2004-11-30 14:59:50.01 spid3 Starting up database 'master'.
2004-11-30 14:59:52.47 spid3 0 transactions rolled back in database
'master' (1).
2004-11-30 14:59:52.48 spid3 Recovery is checkpointing database 'master'
(1)
2004-11-30 14:59:52.62 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-11-30 14:59:52.63 spid5 Starting up database 'model'.
2004-11-30 14:59:52.76 spid3 Server name is 'OBIWAN'.
2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 7
2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 11
2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 12
2004-11-30 14:59:52.78 server SQL server listening on Shared Memory,
Named Pipes.
2004-11-30 14:59:52.78 server SQL Server is ready for client connections
2004-11-30 14:59:52.78 spid8 Starting up database 'msdb'.
2004-11-30 14:59:52.85 spid9 Starting up database 'pubs'.
2004-11-30 14:59:52.86 spid10 Starting up database 'Northwind'.
2004-11-30 14:59:52.99 spid11 Starting up database 'isoglobal'.
2004-11-30 14:59:53.80 spid5 Clearing tempdb database.
2004-11-30 14:59:54.18 spid9 Starting up database 'vmserver'.
2004-11-30 14:59:54.33 spid10 Starting up database 'vmserver_delivery'.
2004-11-30 14:59:56.76 spid5 Starting up database 'tempdb'.
2004-11-30 14:59:57.02 spid3 Recovery complete.
2004-11-30 15:35:06.94 spid52 Starting up database '3663'.
2004-11-30 15:35:07.47 spid52 Starting up database 'demo'.
2004-11-30 15:35:07.81 spid52 Starting up database 'fsspda'.
2004-11-30 15:35:10.27 spid51 Starting up database '3663'.
2004-11-30 15:35:26.30 spid51 Starting up database 'demo'.
2004-11-30 15:35:45.90 spid51 Starting up database 'fsspda'.
2004-11-30 15:36:09.88 spid51 Starting up database '3663'.
2004-11-30 15:36:27.73 spid51 Starting up database 'demo'.
2004-11-30 15:36:45.81 spid51 Starting up database 'fsspda'.
2004-11-30 15:37:24.86 spid51 Starting up database 'demo'.
2004-11-30 15:37:43.23 spid51 Starting up database 'demo'.
2004-11-30 15:38:03.14 spid51 Starting up database 'demo'.
2004-11-30 15:50:39.57 spid53 Using 'xpstar.dll' version '2000.80.194' to
execute extended stored procedure 'sp_MSgetversion'.
2004-11-30 15:50:56.32 spid53 Starting up database '3663'.
2004-11-30 15:50:56.79 spid53 Starting up database 'fsspda'.
2004-11-30 15:50:57.26 spid53 Starting up database '3663'.
2004-11-30 15:51:13.34 spid53 Starting up database 'fsspda'.
2004-11-30 15:51:27.99 spid53 Starting up database '3663'.
2004-11-30 15:51:43.49 spid53 Starting up database 'fsspda'.
2004-11-30 15:51:59.48 spid53 Starting up database '3663'.
2004-11-30 15:52:22.68 spid53 Starting up database 'fsspda'.
2004-11-30 15:52:40.95 spid53 Starting up database '3663'.
2004-11-30 15:53:01.00 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:16.65 spid53 Starting up database '3663'.
2004-11-30 15:53:33.17 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:48.53 spid53 Starting up database '3663'.
2004-11-30 15:53:49.39 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:50.02 spid53 Starting up database '3663'.
2004-11-30 15:53:50.78 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:51.56 spid53 Starting up database '3663'.
2004-11-30 15:53:52.22 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:52.53 spid53 Starting up database '3663'.
2004-11-30 15:53:52.87 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:53.16 spid53 Starting up database '3663'.
2004-11-30 15:53:53.52 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:53.87 spid53 Starting up database '3663'.
2004-11-30 15:53:54.19 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:54.49 spid53 Starting up database '3663'.
2004-11-30 15:53:54.97 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:55.33 spid53 Starting up database '3663'.
2004-11-30 15:53:55.68 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:56.01 spid53 Starting up database '3663'.
2004-11-30 15:53:56.90 spid53 Starting up database 'fsspda'.
2004-11-30 15:53:57.45 spid53 Starting up database '3663'.
2004-11-30 15:53:57.81 spid53 Starting up database 'fsspda'.
2004-11-30 15:54:04.61 spid51 Starting up database 'fsspda'.
2004-11-30 15:54:05.02 spid51 Starting up database 'fsspda'.
2004-11-30 15:54:05.45 spid51 Starting up database 'fsspda'.
2004-11-30 15:54:09.62 spid51 Starting up database '3663'.
2004-11-30 15:54:10.05 spid51 Starting up database 'demo'.
2004-11-30 15:54:17.14 spid51 Starting up database 'demo'.
2004-11-30 15:54:17.46 spid51 Starting up database 'demo'.
2004-11-30 15:54:17.82 spid51 Starting up database 'demo'.
2004-11-30 15:54:33.58 spid53 Starting up database 'Route'.
2004-11-30 15:54:34.32 spid53 Starting up database '3663'.
2004-11-30 15:54:34.76 spid53 Starting up database 'fsspda'.
2004-11-30 15:54:35.07 spid53 Starting up database '3663'.
2004-11-30 15:54:35.38 spid53 Starting up database 'fsspda'.
2004-11-30 15:58:19.63 spid51 Starting up database '3663'.
2004-11-30 15:58:37.12 spid51 Starting up database 'fsspda'.
2004-11-30 15:58:52.46 spid51 Starting up database '3663'.
2004-11-30 15:59:09.98 spid51 Starting up database 'demo'.
2004-11-30 15:59:41.81 spid51 Starting up database 'fsspda'.
2004-11-30 15:59:59.34 spid51 Starting up database '3663'.
2004-11-30 16:00:15.76 spid51 Starting up database 'demo'.
2004-11-30 16:00:50.61 spid51 Starting up database 'fsspda'.
2004-11-30 16:00:51.36 spid51 Starting up database '3663'.
2004-11-30 16:01:10.96 spid51 Starting up database 'demo'.
2004-11-30 16:01:30.14 spid51 Starting up database 'fsspda'.
2004-11-30 16:01:45.79 spid51 Starting up database '3663'.
2004-11-30 16:02:01.59 spid51 Starting up database 'demo'.
2004-11-30 16:02:05.37 spid51 Starting up database 'fsspda'.
2004-11-30 16:02:21.41 spid51 Starting up database '3663'.
2004-11-30 16:02:38.84 spid51 Starting up database 'demo'.
2004-11-30 16:02:58.05 spid51 Starting up database 'fsspda'.
2004-11-30 16:03:13.71 spid51 Starting up database '3663'.
2004-11-30 16:03:34.68 spid51 Starting up database 'demo'.
2004-11-30 16:03:56.00 spid51 Starting up database 'fsspda'.
2004-11-30 16:04:12.85 spid51 Starting up database '3663'.
2004-11-30 16:04:29.93 spid51 Starting up database 'demo'.
2004-11-30 16:04:50.03 spid51 Starting up database 'fsspda'.
2004-11-30 16:05:06.56 spid51 Starting up database '3663'.
2004-11-30 16:05:24.32 spid51 Starting up database 'demo'.
2004-11-30 16:05:51.91 spid53 Starting up database '3663'.
2004-11-30 16:06:10.79 spid51 Starting up database 'fsspda'.
2004-11-30 16:06:26.38 spid53 Starting up database 'demo'.
2004-11-30 16:06:46.93 spid51 Starting up database '3663'.
2004-11-30 16:07:05.64 spid53 Starting up database 'fsspda'.
2004-11-30 16:07:21.08 spid51 Starting up database 'demo'.
2004-11-30 16:07:22.29 spid51 Starting up database 'fsspda'.
2004-11-30 16:07:40.60 spid51 Starting up database '3663'.
2004-11-30 16:07:59.85 spid51 Starting up database 'demo'.
2004-11-30 16:08:25.22 spid51 Starting up database 'fsspda'.
2004-11-30 16:08:44.40 spid51 Starting up database '3663'.
2004-11-30 16:09:02.97 spid51 Starting up database 'demo'.
2004-11-30 16:09:34.28 spid51 Starting up database 'fsspda'.
2004-11-30 16:12:52.66 spid51 Starting up database 'fsspda'.
2004-11-30 16:12:53.04 spid51 Starting up database 'demo'.
2004-11-30 16:12:53.45 spid51 Starting up database '3663'.
2004-11-30 16:12:56.66 spid52 Starting up database 'fsspda'.Neither...it's from having auto close turned on. See my
posts to your same question in the server newsgroup.
-Sue
On Tue, 30 Nov 2004 09:45:07 -0800, "McFly"
<McFly@.discussions.microsoft.com> wrote:

> I have SQL installed locally, and it has been working fine for some time.
> However, today when I went to Enterprise Manager I could see the tree view
> but as soon as I selected "Databases" everything froze, Task Manager
> reported that the application was not responding. I left it for 10 minute
s
>and the
> screen stayed stuck with the hourglass.
> I tried re-starting the SQL service and rebooting the box, but the same
> problem occured.
> When I try and use Query Analyser, I cannot select a database from the
> drop down list, but, I can use the "Use" command to choose a database and
I
>can
> run a query. It is unblievably slow though.
>Just tried to create a new ODBC connection and the test failed because of a
>timeout.
>
> Does anyone have any clues?
>I've posted the log below
>thanks
>J
>2004-11-30 14:59:48.59 server Microsoft SQL Server 2000 - 8.00.194
>(Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
>2004-11-30 14:59:48.60 server Copyright (C) 1988-2000 Microsoft
>Corporation.
>2004-11-30 14:59:48.60 server All rights reserved.
>2004-11-30 14:59:48.60 server Server Process ID is 1636.
>2004-11-30 14:59:48.60 server Logging SQL Server messages in file
>'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>2004-11-30 14:59:48.66 server SQL Server is starting at priority class
>'normal'(1 CPU detected).
>2004-11-30 14:59:49.44 server SQL Server configured for thread mode
>processing.
>2004-11-30 14:59:49.49 server Using dynamic lock allocation. [2500]
Lock
>Blocks, [5000] Lock Owner Blocks.
>2004-11-30 14:59:49.55 server Attempting to initialize Distributed
>Transaction Coordinator.
>2004-11-30 14:59:49.96 server Failed to obtain
>TransactionDispenserInterface: Result Code = 0x8004d01b
>2004-11-30 14:59:50.01 spid3 Starting up database 'master'.
>2004-11-30 14:59:52.47 spid3 0 transactions rolled back in database
>'master' (1).
>2004-11-30 14:59:52.48 spid3 Recovery is checkpointing database 'master
'
>(1)
>2004-11-30 14:59:52.62 server Using 'SSNETLIB.DLL' version '8.0.194'.
>2004-11-30 14:59:52.63 spid5 Starting up database 'model'.
>2004-11-30 14:59:52.76 spid3 Server name is 'OBIWAN'.
>2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 7
>2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 11
>2004-11-30 14:59:52.76 spid3 Skipping startup of clean database id 12
>2004-11-30 14:59:52.78 server SQL server listening on Shared Memory,
>Named Pipes.
>2004-11-30 14:59:52.78 server SQL Server is ready for client connections
>2004-11-30 14:59:52.78 spid8 Starting up database 'msdb'.
>2004-11-30 14:59:52.85 spid9 Starting up database 'pubs'.
>2004-11-30 14:59:52.86 spid10 Starting up database 'Northwind'.
>2004-11-30 14:59:52.99 spid11 Starting up database 'isoglobal'.
>2004-11-30 14:59:53.80 spid5 Clearing tempdb database.
>2004-11-30 14:59:54.18 spid9 Starting up database 'vmserver'.
>2004-11-30 14:59:54.33 spid10 Starting up database 'vmserver_delivery'.
>2004-11-30 14:59:56.76 spid5 Starting up database 'tempdb'.
>2004-11-30 14:59:57.02 spid3 Recovery complete.
>2004-11-30 15:35:06.94 spid52 Starting up database '3663'.
>2004-11-30 15:35:07.47 spid52 Starting up database 'demo'.
>2004-11-30 15:35:07.81 spid52 Starting up database 'fsspda'.
>2004-11-30 15:35:10.27 spid51 Starting up database '3663'.
>2004-11-30 15:35:26.30 spid51 Starting up database 'demo'.
>2004-11-30 15:35:45.90 spid51 Starting up database 'fsspda'.
>2004-11-30 15:36:09.88 spid51 Starting up database '3663'.
>2004-11-30 15:36:27.73 spid51 Starting up database 'demo'.
>2004-11-30 15:36:45.81 spid51 Starting up database 'fsspda'.
>2004-11-30 15:37:24.86 spid51 Starting up database 'demo'.
>2004-11-30 15:37:43.23 spid51 Starting up database 'demo'.
>2004-11-30 15:38:03.14 spid51 Starting up database 'demo'.
>2004-11-30 15:50:39.57 spid53 Using 'xpstar.dll' version '2000.80.194' t
o
>execute extended stored procedure 'sp_MSgetversion'.
>2004-11-30 15:50:56.32 spid53 Starting up database '3663'.
>2004-11-30 15:50:56.79 spid53 Starting up database 'fsspda'.
>2004-11-30 15:50:57.26 spid53 Starting up database '3663'.
>2004-11-30 15:51:13.34 spid53 Starting up database 'fsspda'.
>2004-11-30 15:51:27.99 spid53 Starting up database '3663'.
>2004-11-30 15:51:43.49 spid53 Starting up database 'fsspda'.
>2004-11-30 15:51:59.48 spid53 Starting up database '3663'.
>2004-11-30 15:52:22.68 spid53 Starting up database 'fsspda'.
>2004-11-30 15:52:40.95 spid53 Starting up database '3663'.
>2004-11-30 15:53:01.00 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:16.65 spid53 Starting up database '3663'.
>2004-11-30 15:53:33.17 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:48.53 spid53 Starting up database '3663'.
>2004-11-30 15:53:49.39 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:50.02 spid53 Starting up database '3663'.
>2004-11-30 15:53:50.78 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:51.56 spid53 Starting up database '3663'.
>2004-11-30 15:53:52.22 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:52.53 spid53 Starting up database '3663'.
>2004-11-30 15:53:52.87 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:53.16 spid53 Starting up database '3663'.
>2004-11-30 15:53:53.52 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:53.87 spid53 Starting up database '3663'.
>2004-11-30 15:53:54.19 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:54.49 spid53 Starting up database '3663'.
>2004-11-30 15:53:54.97 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:55.33 spid53 Starting up database '3663'.
>2004-11-30 15:53:55.68 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:56.01 spid53 Starting up database '3663'.
>2004-11-30 15:53:56.90 spid53 Starting up database 'fsspda'.
>2004-11-30 15:53:57.45 spid53 Starting up database '3663'.
>2004-11-30 15:53:57.81 spid53 Starting up database 'fsspda'.
>2004-11-30 15:54:04.61 spid51 Starting up database 'fsspda'.
>2004-11-30 15:54:05.02 spid51 Starting up database 'fsspda'.
>2004-11-30 15:54:05.45 spid51 Starting up database 'fsspda'.
>2004-11-30 15:54:09.62 spid51 Starting up database '3663'.
>2004-11-30 15:54:10.05 spid51 Starting up database 'demo'.
>2004-11-30 15:54:17.14 spid51 Starting up database 'demo'.
>2004-11-30 15:54:17.46 spid51 Starting up database 'demo'.
>2004-11-30 15:54:17.82 spid51 Starting up database 'demo'.
>2004-11-30 15:54:33.58 spid53 Starting up database 'Route'.
>2004-11-30 15:54:34.32 spid53 Starting up database '3663'.
>2004-11-30 15:54:34.76 spid53 Starting up database 'fsspda'.
>2004-11-30 15:54:35.07 spid53 Starting up database '3663'.
>2004-11-30 15:54:35.38 spid53 Starting up database 'fsspda'.
>2004-11-30 15:58:19.63 spid51 Starting up database '3663'.
>2004-11-30 15:58:37.12 spid51 Starting up database 'fsspda'.
>2004-11-30 15:58:52.46 spid51 Starting up database '3663'.
>2004-11-30 15:59:09.98 spid51 Starting up database 'demo'.
>2004-11-30 15:59:41.81 spid51 Starting up database 'fsspda'.
>2004-11-30 15:59:59.34 spid51 Starting up database '3663'.
>2004-11-30 16:00:15.76 spid51 Starting up database 'demo'.
>2004-11-30 16:00:50.61 spid51 Starting up database 'fsspda'.
>2004-11-30 16:00:51.36 spid51 Starting up database '3663'.
>2004-11-30 16:01:10.96 spid51 Starting up database 'demo'.
>2004-11-30 16:01:30.14 spid51 Starting up database 'fsspda'.
>2004-11-30 16:01:45.79 spid51 Starting up database '3663'.
>2004-11-30 16:02:01.59 spid51 Starting up database 'demo'.
>2004-11-30 16:02:05.37 spid51 Starting up database 'fsspda'.
>2004-11-30 16:02:21.41 spid51 Starting up database '3663'.
>2004-11-30 16:02:38.84 spid51 Starting up database 'demo'.
>2004-11-30 16:02:58.05 spid51 Starting up database 'fsspda'.
>2004-11-30 16:03:13.71 spid51 Starting up database '3663'.
>2004-11-30 16:03:34.68 spid51 Starting up database 'demo'.
>2004-11-30 16:03:56.00 spid51 Starting up database 'fsspda'.
>2004-11-30 16:04:12.85 spid51 Starting up database '3663'.
>2004-11-30 16:04:29.93 spid51 Starting up database 'demo'.
>2004-11-30 16:04:50.03 spid51 Starting up database 'fsspda'.
>2004-11-30 16:05:06.56 spid51 Starting up database '3663'.
>2004-11-30 16:05:24.32 spid51 Starting up database 'demo'.
>2004-11-30 16:05:51.91 spid53 Starting up database '3663'.
>2004-11-30 16:06:10.79 spid51 Starting up database 'fsspda'.
>2004-11-30 16:06:26.38 spid53 Starting up database 'demo'.
>2004-11-30 16:06:46.93 spid51 Starting up database '3663'.
>2004-11-30 16:07:05.64 spid53 Starting up database 'fsspda'.
>2004-11-30 16:07:21.08 spid51 Starting up database 'demo'.
>2004-11-30 16:07:22.29 spid51 Starting up database 'fsspda'.
>2004-11-30 16:07:40.60 spid51 Starting up database '3663'.
>2004-11-30 16:07:59.85 spid51 Starting up database 'demo'.
>2004-11-30 16:08:25.22 spid51 Starting up database 'fsspda'.
>2004-11-30 16:08:44.40 spid51 Starting up database '3663'.
>2004-11-30 16:09:02.97 spid51 Starting up database 'demo'.
>2004-11-30 16:09:34.28 spid51 Starting up database 'fsspda'.
>2004-11-30 16:12:52.66 spid51 Starting up database 'fsspda'.
>2004-11-30 16:12:53.04 spid51 Starting up database 'demo'.
>2004-11-30 16:12:53.45 spid51 Starting up database '3663'.
>2004-11-30 16:12:56.66 spid52 Starting up database 'fsspda'.
>

IS THERE ANY TOOL

Is there any tool like Enterprise Manager to help me create databases , tables ... with MSDE?
If there isn't how can i create these objects?
Perhaps using OSQL Command?
Thank you
George
> Is there any tool like Enterprise Manager to help me create databases
> , tables ... with MSDE? If there isn't how can i create these objects?
> Perhaps using OSQL Command?
A good list here:
http://www.microsoft.com/sql/msde/partners/default.asp
I strongly recommend our tool : myLittleAdmin
(http://www.mylittletools.net/mla_sql)
Sincerely
el.c.
// myLittleTools.net : leading provider of web-based applications.
// myLittleAdmin : online MS SQL manager
// http://www.mylittletools.net
// webmaster@.mylittletools.net
|||I use SQL Server Web Data Administrator (free stuff), and
it is really cool!
To help you, I will show were to find the software in the
correct order of installation:
..Microsoft .NET Framework Version 1.1
Redistributable Package
http://www.microsoft.com/downloads/details.aspx?
FamilyID=262d25e3-f589-4842-8157-
034d1e7cf3a3&displaylang=en
..Microsoft .NET Framework SDK Version 1.1
http://www.microsoft.com/downloads/details.aspx?
FamilyID=9b3a2ca6-3647-4070-9f41-
a333c6b9181d&displaylang=en
..ASP.NET Cassini Sample Web Server
http://asp.net/Projects/Cassini/Download/Default.aspx?
tabindex=0&tabid=1
..Microsoft SQL Web Data Administrator
http://www.microsoft.com/downloads/details.aspx?
FamilyId=C039A798-C57A-419E-ACBC-
2A332CB7F959&displaylang=en
Good luck!
Aldrin
PS INSTALL SOFTWARE PACKAGES IN THIS ORDER!
[color=darkblue]
>--Original Message--
create databases[color=darkblue]
create these objects?
>A good list here:
>http://www.microsoft.com/sql/msde/partners/default.asp
>I strongly recommend our tool : myLittleAdmin
>(http://www.mylittletools.net/mla_sql)
>Sincerely
>el.c.
>--
>// myLittleTools.net : leading provider of web-based
applications.
>// myLittleAdmin : online MS SQL manager
>// http://www.mylittletools.net
>// webmaster@.mylittletools.net
>
>.
>
|||The Developer edition of SQL Server is available for $49 from
Microsoft, which has all of the client tools (SEM, QA, Profiler,
etc.), which you can install independently of the server.
--mary
On Tue, 13 Apr 2004 02:51:03 -0700, GEORGE
<anonymous@.discussions.microsoft.com> wrote:

>Is there any tool like Enterprise Manager to help me create databases , tables ... with MSDE?
>If there isn't how can i create these objects?
>Perhaps using OSQL Command?
>Thank you
>George

Is there any reported issues running SQL Server 2005 Enterprise 64bit Management Studio version?

At the moment I'm trying to find out if there are any reported issues with Management Studio running on a SQL Server 2005 Ent 64bit edition?

Can anyone help?

My reason for asking is really one of curiosity, one of my colleagues has said it doesn't work, I'm trying to research this claim as I do not have access to a 64 bit machine to try it on but would like to move my future project in this direction hence why I'm asking.

Many Thanks.

Dave

Hi Dave,

Technically, there aren't different versions of Management Studio, only 1 (client tools are distributed with all editions, except Express)...though, there are different platform builds (i.e. IA64,x64,x86)...

Management studio with Sql2k5 is fully 64bit compatible, and will run natively on an IA64 or x64 box...

HTH

|||There are issuses with SQL Server 2005 64 bit and the Management Studio that are explained here http://support.microsoft.com/default.aspx/kb/906892.
The Management Studio will run on the 64 bit platform but it will be slow and tend to freeze, the reason being it's still a 32 bit application. MS solution is to run the Management Studio on a 32 bit computer and connect to the SQL server that way. Why they don't have a 64 bit version of the Management Studio is anyone's guess.
RLB

Is there any reported issues running SQL Server 2005 Enterprise 64bit Management Studio version?

At the moment I'm trying to find out if there are any reported issues with Management Studio running on a SQL Server 2005 Ent 64bit edition?

Can anyone help?

My reason for asking is really one of curiosity, one of my colleagues has said it doesn't work, I'm trying to research this claim as I do not have access to a 64 bit machine to try it on but would like to move my future project in this direction hence why I'm asking.

Many Thanks.

Dave

Hi Dave,

Technically, there aren't different versions of Management Studio, only 1 (client tools are distributed with all editions, except Express)...though, there are different platform builds (i.e. IA64,x64,x86)...

Management studio with Sql2k5 is fully 64bit compatible, and will run natively on an IA64 or x64 box...

HTH

|||There are issuses with SQL Server 2005 64 bit and the Management Studio that are explained here http://support.microsoft.com/default.aspx/kb/906892.
The Management Studio will run on the 64 bit platform but it will be slow and tend to freeze, the reason being it's still a 32 bit application. MS solution is to run the Management Studio on a 32 bit computer and connect to the SQL server that way. Why they don't have a 64 bit version of the Management Studio is anyone's guess.
RLB