November 28, 2005 at 12:07 pm
I came in this morning and found that SQL Server services had restarted. I spoke with others and no one says they did anything. There were no logs stating any errors or problems. In fact, the first log of the day was the request to restart services:
"SQL Server is terminating due to 'stop' request from Service Control Manager."
Why and how would SQL restart itself automatically? I am still looking for clues but nothing sticks out.
Thanks!
November 28, 2005 at 12:46 pm
I would be $$ that someone restarted it and is not telling you. SQL does not restart itself
A.J.
DBA with an attitude
November 28, 2005 at 2:10 pm
Not to differ with my esteemed colleague, but I have seen instances where the service restarted itself. This mostly happened with SQL Server 7.0 but sometimes, a user would do something to kick off an errant process and the log would begin to fill with what looked like a memory dump, then the service would restart. Never did find the cause and it didn't happen often, but it pretty much went away with SQL 2000.
Another thing to check - the service would restart if it's set to start automatically and if the server itself rebooted for whatever reason. What about your server event logs? Is there anything indicating a restart of the server or SQL?
My hovercraft is full of eels.
November 28, 2005 at 11:40 pm
The Stop Request came from Service Control Manager ? I'll bet someone elses bottom dollar that this was not an automatic shutdown. UNLESS it's clustered and the cluster stopped the service - can't test this to see what is recorded in the log.
DB
The systems fine with no users loggged in. Can we keep it that way ?br>
November 29, 2005 at 7:13 am
It could be an automatic update or patch from Windows that caused it to reboot, if your system allows auto update.
November 29, 2005 at 11:56 am
You didn't experience any space issues with that server....
November 29, 2005 at 3:18 pm
Perhaps you could supply us with some config details such as SQL ver, SP level, OS platform (XP, 2000 etc). Is it clustered ?
Or have you found the guilty party ?
The systems fine with no users loggged in. Can we keep it that way ?br>
November 29, 2005 at 3:36 pm
Check the event logs in Windows. The application and system event logs may give you an idea of why SQL Server went down if it wasn't a person doing it. If it was a person and you've got both success and failure auditing on for account logins, etc., you may be able to see someone establishing either a local login (say through TS or Remote Desktop) or a network login (if just connecting and restarting the service remotely).
K. Brian Kelley
@kbriankelley
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply