> Sql Server
> SQL Server 2000 (SP3a) Crashing
SQL Server 2000 (SP3a) Crashing
I think I explained the crashes a bit wrong before maybe ... Removing the named-pipes protcol does not seem to have resolved this nasty problem this time round. Removing from the Enterprise manager (button at bottom in general settings tab), network protcol "named pipes", and from client connection settings manager, so that only TCP/IP is allowed as a network What does a massive duration on Event Type 15 mean?! check over here
Memory leak ? My theory is that these pipes become blocked, and this causes 100% CPU usage. Compression disabled. The other case I've seen was with some poor SQL.
The "cannot allocate" space errors that occured last night have now stopped. It takes just 2 minutes to sign up (and it's free!). All Rights Reserved. Within about an hour or two, the symptoms of a big slow-down came back with CPU 100%.
What does a massive > > duration on Event Type 15 mean?! cant connect to Sql server 2000 sp3a in windows 2003 server 11. When starting does it start up quickly or take time? directory Not even sure I'd call it a hang.
I know of two way this can happen. It hurts performance, but returns to normal. If this happens, you should see this in the error log, where you get a load of these messages. But it does indicate that perhaps your transactions are lasting for two long.
No, please don't ask me what that clue would mean! this content Theres no indication in the errorlogs, as to what happens just before the 'crash'. I now regularly look at the sp_lock page and the "processes" page. crashes often 11.
Removing from the Enterprise manager (button at bottom in general settings tab), network protcol "named pipes", and from client connection settings manager, so that only TCP/IP is allowed as a network check my blog And stays that way for a few seconds or more. 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 My correspondence chess website www.chessworld.net makes heavy use of SQL Server 2000.
During this time, deletes and updates can generally be performed, but basically any additional inserts will be blocked while the space is allocated. (and any updates or deletes that need to Also, this can occur a lot with transaction logs. What happens if you wait? (how long do you wait before cycling it?) Best Regards Thue Jul 20 '05 #10 P: n/a Tryfon Gavriel Thank you Greg and Erland I ran http://htbsoftware.com/sql-server/sql-server-2000.html Consider this, let's say (and this is a wild guess here) you're supporting 1 million users.
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. Hi there Thank you for that feedback. Keep in mind it's perfectly possible to be using 100% of the CPU and it not be a bug etc.
Tryfon Gavriel (firstname.lastname@example.org) writes: > (The first six are all event type 15 - which is "Disconnect" i believe. > They have massive duration times, and massive values for Reads.) >...
But there are probably more possibilities than these two. You will need to call PSS to get the fix, but for bugs calls are free or at least refunded immediately. -- Darren Green (SQL Server MVP) DTS - http://www.yqcomputer.com/ Can anybody give me a clue as to what i should do ? One way to track down the latter is to have a profiler trace running, and see what you get just before the machine goes into nirvana. -- Erland Sommarskog, SQL Server
depending on the size and type of DB). All errorlogs begin with info regarding the startup of sqlserver initialising the listener and starting up the db´s and such. Yeah. have a peek at these guys It is possible that the SQL statements you see when you sort on Duration has anything to do with the CPU hog.
Ok. Good. I will request a database server reboot and increase their sizes again. 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
You can't delete your own posts. It was then that I increased the size, but also put auto-grow on. Please do. The idea was to highlight potential processes that could be killed.
So it's most likely the tempdb or the chessworld one. (as he states the obvious.) I was not exactly sure if it was a) or b) but I have more evidence I´m maintaining a large intranet (approx 10000 concurrent users) running on one IIS box and one DB box with sqlserver 2000. Just the above. My analysis of disk usage, queues etc.
Duration is just how long the connection was open. Nope, never seen that happen.
© Copyright 2017 htbsoftware.com. All rights reserved.