June 10, 2011 at 10:16 am
We have a heavy transactional database on a SQL 2008 server (Enterprise) with Windows 2003 Server R2 SP2. We are planning for a maintenance this weekend. I would like to know if there is any difference between:
(a) stop the SQL Service first then shutdown the server
(b) Start ==> Shutdown
Thanks in advance.
June 10, 2011 at 10:45 am
Probably no difference because starting the shut down process on the server is going to start the shut down process on SQL Server. But I would still do it by shutting down SQL Server just so I'm maintaining control of the process. Probably silly paranoia on my part, but there it is.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 10, 2011 at 1:17 pm
I agree with Grant; best to first stop the SQL services and then restart the server, just to be on safe side.
You never know if by some bad stroke of luck, Windows did not shut down the SQL properly and then you end up with a corrupted instance etc.
Also, are there any critical SQL jobs that might be running during the outage window?
Best to disable those before the outage, and then re-enable and manually run after.
Otherwise, you could have unpleasant application failures the next day.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
June 10, 2011 at 2:13 pm
I prefer solution (a) as well because we don't really know how OS terminate the SQL service.
Thanks to both of you and have a nice weekend.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply