SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Restart - Reason


SQL Server Restart - Reason

Author
Message
dva2007
dva2007
SSCarpal Tunnel
SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)

Group: General Forum Members
Points: 4978 Visits: 1394
Hi there

We had sql server restarted unexpectedly and i am trying to find the reason. In my experience (I am not DBA) with SQL Server there is one instance in the past with different employer where the server restarted and DBA said it was because of memory pressure. However technical architect said it is not possible for sql server to restart on its own because of memory pressure. We never found the reason at that time but this time i am trying to find out the reason. It is good to start perhaps with error log file and i can see what happened just before restart and after restart. I am trying to interpret the reason and all i can see is memory pressure. Is it possible that because of memory pressure it has restarted? I cant see any specific user. The restart time was exact mid night.

I've attached the log file for reference. Updated few names by XXXX or RRRR etc.

Thanks.
Attachments
Error Log.txt (16 views, 10.00 KB)
anthony.green
anthony.green
SSC Guru
SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)SSC Guru (77K reputation)

Group: General Forum Members
Points: 77305 Visits: 8654
What do the application and system event logs say for around the same time period?



How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger


SQL Surfer '66
SQL Surfer '66
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3822 Visits: 449
I don't think the memory pressure is the cause of the restart. Your error log says:

2017-12-06 23:59:38.81 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2017-12-06 23:59:38.88 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

SQL Server was stopped due to server shutdown. Have you checked the event logs as anthony.green said to see why the server was shutdown?
dva2007
dva2007
SSCarpal Tunnel
SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)

Group: General Forum Members
Points: 4978 Visits: 1394
Attached logs event.
Attachments
Event Log.docx (17 views, 219.00 KB)
SQL Surfer '66
SQL Surfer '66
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3822 Visits: 449
That doesn't look good. You didn't mention the cluster. I'm definitely no cluster expert, so I can't tell from the attached logs if the cluster has communication problems or SQL Server made the cluster resource fail. Are you a Windows and/or cluster admin? If not have anyone in your organisation taken a look at it? Perhaps the cluster has more logs?

Is this happening frequently?
dva2007
dva2007
SSCarpal Tunnel
SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)

Group: General Forum Members
Points: 4978 Visits: 1394
I have sys admin permission because i am helping with migration project however i never had admin responsibility. I am not windows admin. I can ask someone to look but i need to guide them about what to do and what to check.

Regarding frequency, i am told it happened about 2 years ago and it happened about 3-4 times in last 5 years.
SQL Surfer '66
SQL Surfer '66
Hall of Fame
Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)Hall of Fame (3.8K reputation)

Group: General Forum Members
Points: 3822 Visits: 449
By the attached logs I see you're running SQL Server 2005 on Windows Server 2003 (R2). Is it on old hardware too? Maybe that's the problem?

The system and application logs doesn't tell much. The communication errors seems to correlate with the cluster resource failing. Does the cluster have any logs you can look into?

Judging by the frequency you're experiencing this problem my recommendation is to start migrating your database environment to newer versions of SQL Server and Windows Server instead.
dva2007
dva2007
SSCarpal Tunnel
SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)SSCarpal Tunnel (5K reputation)

Group: General Forum Members
Points: 4978 Visits: 1394
Thanks. Yes it is running SQL 2005 and Windows 2003. I think hardware is 8 years old. Perhaps that is a problem but until we finish migration we just need to continue with current server. I will check with DBA for log files. We are doing migration at the moment.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search