SQL 2000 SP 4 Not Starting - Hanging

[ABerkowicz]

Hi - All of a sudden, a sql server with SP 4 on Win Serv 2003 SP 2 is hanging. I cannot launch SQL services without causing server to hang. Server is fine until SQL 2000 services start - It appears that the databases start up and that perhaps it is hanging at tempdb. I saw the error before that tempdb log is full - but now when sql services are started it only lasts for like 30 seconds and I cannot do anything - and have to reboot server. Any ideas on how to troubleshoot as I believe that rebooting should take care of tempdb issue by clearing it out. Is there any way to disable the startup of tempdb perhaps? or maybe read only or any other ideas?? Thanks!

 

[mrdenny]

What shows up in the errorlog file? How about the Application log?

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[ABerkowicz]

I should have said this initially - nothing is listed in Application log or sql log for an error. I finally got SQL to start after waiting 1/2 hour - so there must be a memory leak - related/unrelated to SQL I do not know. So, I have to see if there are any ways to capture memory leaks - I guess I have to get the net admin individuals as this my/may not be SQL related. Thanks.

 

[mrdenny]

I've never heard of SQL locking up the machine which it's starting. If there was a disk problem I could see it causing the server to respond like that while SQL is starting as SQL hits the disk a lot while it starts. Same goes for a RAM problem.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[ABerkowicz]

Thank you for the information. I have a call to Microsoft and they have put OS tools and SQL tools - so hopefully we will know what is causing the problem. I tend to agree that maybe it is a hardware issue - thanks!

 

[SQLWilts]

Hmmmm tempdb?

Just a shot in the dark...
the tempdb file isn't held on the C: drive, and has become huge has it?

Try starting SQL server with the -T3608 switch and check out where it is - couldnt hurt to change its initial size to something reasonable and move it to a fast drive.

As I said - just a shot in the dark here