SQL Server 2005 service restarting itself

Question

Post reply

SQL Server 2005 service restarting itself

Denise McMillan

SSCertifiable

Points: 6216
More actions
May 15, 2008 at 11:06 am

#129078

We have a SQL Server 2005 cluster set up, with 2 nodes, on Windows 2003. Lately there has been two times where SQL Service has just restarted itself. I'm having trouble figuring out why. I don't see any errors before it happened either time.
We have been getting this message periodically though: A significant part of sql server process memory has been paged out. This may result in a performance degradation.
Could this be causing the restart of SQL Services?
What else should I look for?
Thanks very much for any ideas.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

sodeep SSC Rookie Points: 34 More actions · Answer 1

Looks like memory issues. Which edition and SP level is it? What else do you see in app log?

Denise McMillan SSCertifiable Points: 6216 More actions · Answer 2

The SQL Server is enterprise ed, sp 2. Windows is 2003 enterprise x64 ed.

Matt Miller (4) SSC Guru Points: 124210 More actions · Answer 3

Have you locked pages in memory? See this document:

http://support.microsoft.com/kb/918483

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 4

Did you also apply Cumulative update 5 ?

I wouldn't advise CU6 because it has some start/stop issues with SSCM

(Unless you actualy want some fixes it contains)

- Are you using CLR ?

- Can you find anything in SQLServer errorlog ?

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Matt Miller (4) SSC Guru Points: 124210 More actions · Answer 5

ALZDBA (5/15/2008)
Did you also apply Cumulative update 5 ?
I wouldn't advise CU6 because it has some start/stop issues with SSCM
(Unless you actualy want some fixes it contains)
- Are you using CLR ?
- Can you find anything in SQLServer errorlog ?

For what it's worth....CU7 is also out. Don't know anything about it, so read up and see if it applies....

http://support.microsoft.com/kb/949095

----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

Denise McMillan SSCertifiable Points: 6216 More actions · Answer 6

I have read the document you mentioned on locking pages in memory but haven't done that yet. Not sure I fully understand the affects it would have.

I also haven't installed CU 5, 6 or 7. I'm not sure how I would know if any of these hot fixes address whatever problem I have.

We do not have clr configured.

What's the best way to tackle this? How can I tell which of these suggestions will be right?

I can try running a trace on the counters mentioned in the article, though my skill in interpreting them may not be very good.

Thank you all so much for the help with this.

Johan Bijnens SSC Guru Points: 135369 More actions · Answer 7

You need at least CU1 if you have maintenance plans in use, because that one fixes issues with maintenance plans.

Currently we are installing CU5 to all our SQL2005 instances and I didn't encounter issues with it (things not working after apply).