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)
 Performance Issues

Author  Topic 

kpsreenath
Yak Posting Veteran

52 Posts

Posted - 2006-04-03 : 14:14:03
Hi All
Last to last friday, the server crashed.We had to restart the machine to bring up the sql server.Initially we thought this as a one odd instance.This friday, almost the same time, it crashed again. By the time users complained saying they are not able to acces the application, the server froze.I was not able to see the processes running during this time.
Now I realised there is a potential problem.
I check all the logs - > SQL Server log, SQL Agent log, Event viewer.
I dont see any error messages related to this.
Since both weekends it happened at the same time, I assume that there might be some job running on the friday evening which is bringing the server down.
I checked for all the scheduled jobs and didnt find anything. So I assume this might be because of some adhoc jobs ran from the application which is causing this issue.
This have been highly escalated by the users and I have to act.
I am planning to put a trace to see the happenings during this time.
Questions
1) What all parameters(in the profiler) should i take into consideration
2) Any other ways of troubleshooting the same.
3) Any whitepapers / documents to similar issues
Plz respond,my job is at stake

Thanks
Sree

Hommer
Aged Yak Warrior

808 Posts

Posted - 2006-04-03 : 16:59:41

Performance monitor is another tool.

Following is a link I found when I googled a similar issue a while back.

http://vyaskn.tripod.com/analyzing_profiler_output.htm

Good luck!
Go to Top of Page

bakerjon
Posting Yak Master

145 Posts

Posted - 2006-04-06 : 10:46:21
You might want to think about a blackbox trace.

DECLARE @TraceID int

EXEC CreateTrace
@Blackbox = 1,
@OutputTraceID = @TraceID OUT

EXEC StartTrace
@TraceID


This gives you some good t-shooting info. You can look at BOL for more info on Blackbox, but it's pretty helpful. I wouldn't leave it on all the time, though.



Jon

Holding it down on the engineering tip, y'all!

http://www.sqljunkies.com/weblog/outerjoin
Go to Top of Page

kpsreenath
Yak Posting Veteran

52 Posts

Posted - 2006-04-06 : 15:34:14
This is the first time i am hearing abt Blackbox trace.I am trying it out..
thanks a lot for the information

Thanks
Sree
Go to Top of Page

mcrowley
Aged Yak Warrior

771 Posts

Posted - 2006-04-07 : 15:57:13
To check if it is a resource contention issue (we had a memory leak in an application that took about 1 week to kill the box), try pre-emptively rebooting the machine on Thursday. If you still have a problem on Friday, it is more likely to be a rogue process/query. If the problem is deferred to next Monday, or Tuesday, you probably have a resource leak of some kind.
Go to Top of Page
   

- Advertisement -