Guillaume Senneville (google2@candg2.com) writes:[color=blue]
> we are having this weird problem that can be reproduced easily on 2
> out of 2 servers where we've tried:
> - we run a SQL Server 2000 stored procedure that processes 2.5 million
> rows (big procedure with many cursors)
> - when it hits an area of procedure (not always the exact same place,
> but in the same area) , the server reboots
>
> I've tried to debug the problem but:
> - there are no event log except when it restarts to say 'previous
> system shutdown unexpected'
> - the blackbox trace I've created is empty
> - the perfmon log stops a few seconds before the reboot and shows no
> out of whack counter
> - we've had the hardware checked by an IT guy and everything looks
> fine[/color]
Well, there are two ways to and you will probably not like any of
them:
1) Open a case with Microsoft. If indeed an error in SQL Server is
causing Windows to reboot, then you should befunded for the case.
Same if the error in Windows.
2) Take a stab of the procedure and rewrite it to use fewer cursors
and to more set-based operations.
Oh, you should also review your crash-dump options for Windows, so
that you save a memory dump when Windows goes down the drain. There is
a program WinDbg that you can download from Microsoft.com to analyse
crash dumps.
My gut feeling is that it is after all a hardware problem, probably a
bad memory board somewhere.
--
Erland Sommarskog, SQL Server MVP,
sommar@algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp 
