Home > Sql Server > SQL Server 2000 (SP3a) Crashing

SQL Server 2000 (SP3a) Crashing

Its very weird, I run performance monitor with counters on, memory, disk usage, num users, locks and such. Do a dbcc checkdb on the database and tempdb.RegardsPeter 0 Quote GriffithsJ GriffithsJ Posted 13 years ago #127098 Forum Newbie Group: General Forum Members Points: 8 Visits: 3 Allen & PeterThere LeovanDoorn posted May 5, 2015 stored procedure Vlad22 posted Apr 18, 2015 New environment, Access 2010... In this particular case I was testing performance of this poor SQL for an article on my web site. navigate here

To my mind, it appears to be completely un-predictable.Griff 0 Quote Peter Tillotson Peter Tillotson Posted 13 years ago #127180 SSC-Addicted Group: General Forum Members Points: 429 Visits: 80 I don't Hope this helps, Stephen Dybing This posting is provided "AS IS" with no warranties, and confers no rights. In itself, not that exciting. An insert is performed.... https://www.exploit-db.com/exploits/16392/

depending on the size and type of DB). And the stop request is issued by me after the system has crashed / is hanging. depending on the size and type of DB).

Thanks for all the answers ! I continually make efforts to optimise all queries used on the site. I would like all possible causes of CPU 100% to be listed somewhere so I can check that I have taken all precautions to avoid this. MMC crashes while using SQL 2000 Enterprise Manager 6.

Best wishes Tryfon "Erland Sommarskog" wrote in message news:Xn**********************@127.0.0.1... The message only appears with SP3 or later hotfixes. Yeah. You can't delete other posts.

The only way to get the site up running again is to restart the sqlserver service (not the server). I continually make efforts to optimise all queries used on the site. The performance monitor also stops getting input and just freezes. I would include the Starting events in the trace, and then investigate the uncompleted events at the end of the trace when the CPU goes 100%. -- Erland Sommarskog, SQL Server

Good. http://www.sqlservercentral.com/Forums/Topic126949-9-1.aspx Hmm, given what yu say, I'm guessing that your tempb may be growing a lot. (Since upon restart I believe it'll get resized back to it's original size.) This could be The only thing that peaks a lot are the locks/sec counter. tells me i got no kind of i/o bottlenecks.

So, I generally try NOT to allow auto-growth, or set it to a fixed amount (like 10MB or 100MB, etc. http://recupsoft.com/sql-server/sql-server-2000-notification-services.html Im maintaining a large intranet (approx 10000 concurrent users) running on one IIS box and one DB box with sqlserver 2000. Which on a production DB is almost always a "bad thing". The other case I've seen was with some poor SQL.

Because the problem transferred to a different windows server it sounds like the problem is probably a corrupt database. Cant say I have ever seen the following before, but that is the third error. * ex_terminator - Last chance exception handling For those who wish to read the full logs I think viewing the sysprocesses table is very useful point of reference, and the reason I started investigating it, is because it is mentioned in SQL Serrver 2000 programming book page his comment is here Select a forum  SQL Server 2016   SQL Server 2016 - Administration   SQL Server 2016 - Development and T-SQL SQL Server 2014   Administration - SQL Server 2014   Development - SQL Server 2014 SQL Server

Privacy Policy. What does a massive duration on Event Type 15 mean?! You can download attachments.

Which is somewhat critical.

Its very weird, I run performance monitor with counters on, memory, disk usage, num users, locks and such. Before you know it, you've got a 10 gig DB trying to allocate 1GB. (and the kicker is, it probably only needs 10MB at that point. :-) And of course during What I mean is that the sqlserver suddenly 'hangs' and that its impossible to communicate with in any way. What I mean is that the sqlserver suddenly 'hangs' and that its impossible to communicate with in any way.

That might give you a clue. The following article thread indicates this:- http://www.mcse.ms/message97673.html which is kind of worrying to me, because I was fairly sure removing Named Pipes as a protocol before, completely cured the CPU 100% There is no indications in the counters before the crashes, they just happen very sudden. http://recupsoft.com/sql-server/sql-server-2000-quad-cpu.html Hi there I share your pain and frustration.

Then again, maybe it is a clue that four long-running processes owned by sa quits just before the machines reaches nirvana. A more detailed explanation for the resolution of this particular item may have been provided in the comments section. 0 0 Sign into vote ID 191177 Comments 3 Status Closed Workarounds The database is also now set to grow by up to 50% if required.I have backed up the database and put it on an "identical" server - same results.I have also I want to resolve the CPU 100% problem myself - I thought I had resolved before but has come back to haunt me now with a new database server machine with

Finally, if this doesn't turn up anything, call Microsoft. I would include the Starting events in the trace, and then investigate the uncompleted events at the end of the trace when the CPU goes 100%. I had to request the database server to be restarted. Currently SQLSERVER 2000 crashes at least once a day.

Sign in to post a workaround. Best wishes Tryfon "Greg D. I also make use of the ASP error object to generate errors in a log file, and my most frequently logged error is now SQL Server related. Moore \(Strider\) "Thue Tuxen Srensen" wrote in message news:3f**********************@dread14.news.tele.dk ...

Check the database growth percentage is large enough for what you need. a relief :) ) Note that a backup will not affect database performance. (or at least the affect is extremely small because of an increased disk I/O.