Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 DBCC CHECKDB Never comes home

Author  Topic 

X002548
Not Just a Number

15586 Posts

Posted - 2003-10-14 : 08:43:23
Hosed? You betcha...

What now? Bounce the box?

No Messages in the Error log...

SPROC Just timed out...left about 10,000 locks..

Killed the spid (probably made it worse)...

Thank god for back ups and it only being a dev enviroment...

Any idea why a busted connection (run in QA) would cause SQL to become hosed?



Brett

8-)

X002548
Not Just a Number

15586 Posts

Posted - 2003-10-14 : 11:12:55
Solution: Take box and bounce it from the 5th floor...

Pretty cool how it recovers its self...even recovered the db, and checkdb shows no errors...

Have no idea what the hell happened...

Yukon HO! Fail over city!



Brett

8-)
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-10-14 : 12:21:53
I had read a while back that you can not kill any spids that are running DBCC statements. I don't remember which version it applied to though. If it is true in 2000, then killing the spid did nothing. It probably just continued running and slowing down the server which then caused other queries to perform badly which caused all of the locks being there longer than they should have.

Tara
Go to Top of Page

X002548
Not Just a Number

15586 Posts

Posted - 2003-10-14 : 12:45:55
quote:
Originally posted by tduggan

I had read a while back that you can not kill any spids that are running DBCC statements. I don't remember which version it applied to though. If it is true in 2000, then killing the spid did nothing. It probably just continued running and slowing down the server which then caused other queries to perform badly which caused all of the locks being there longer than they should have.

Tara



Nah....killed the spid the sproc was running in after it timed out, and was still being seen by sp_who2 active...

I let DBCC CHECKDB run in another window...overnight...15 hours...NOTHING...

Ran it again after the bounce, and everything checked out fine...

set up a trace got all set, ran the sproc..boom...ran like lightning...don't know what was going on...

I hate when that happens...(but I'm so accustomed to it by now)



Thanks for the info Tara..



Brett

8-)
Go to Top of Page
   

- Advertisement -