July 8, 2011 at 4:16 pm
We need to do some maintenance for our SANS, some sql servers needs to be shut down, then later bring up.
What is the best way for gracefully shutting down sql server host?
I know we need to shut down applications/web server first then shut down SQL server.
But specifically for sql server, do I need to shut down SQL service first before shut down the physical server first, or it doesn't make much difference?
Thanks,
July 8, 2011 at 4:40 pm
First make sure there are no more connections being made to the database.
Then shut down the service.
Then go ahead and shut down the server.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 9, 2011 at 3:58 am
shutting down the Windows OS will gracefully shut down all running processes including SQL Server.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 9, 2011 at 5:14 am
just to add to the previous replies...
for such kind of maintenance, I always advise to disable the services ( or take the cluster resources offline ) so they don't auto start when you startup the server(s) and can keep control over the startup of the things you want to.
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
July 11, 2011 at 1:11 am
are you also taking active directory offline?
if so dont power on the sql servers until ad is back online.
our server guys have fallen into this trap many a time, where they have powered all servers on at the same time due to a power outage and SQL wont start due to AD not being ready to authenticate the service accounts.
July 11, 2011 at 3:08 am
anthony.green (7/11/2011)
are you also taking active directory offline?if so dont power on the sql servers until ad is back online.
our server guys have fallen into this trap many a time, where they have powered all servers on at the same time due to a power outage and SQL wont start due to AD not being ready to authenticate the service accounts.
this is something the domain admins should handle but yes, DCs are the last to go down and the first to come up
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 11, 2011 at 3:12 am
totally agree with you on that Perry the domain admins should handle the DC's.
the issue came that once power was restored, all of the servers powered on at exactly the same time and they forgot to manually power off the SQL servers which cause the issues we saw.
July 11, 2011 at 3:21 am
TBH it shouldnt be too much of an issue as the service is normally set to retry 3 times by which time the DC should be available. Its best to get the correct order though, even more important for a cluster as the DC is generally the DNS server too (if you're using AD integrated zones) 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply