July 23, 2012 at 6:24 am
Hi everyone
Can anyone tell me , or point me to any documentation that states why SQL 2008 services should be stopped and started from SQL Server Configuration Manager ?
Sure I have read \ seen something that says MS recommend doing from here as opposed to services window.
many thanks for any tips \ thoughts on the above.
cheers
July 23, 2012 at 6:30 am
Starting the service can be done from anywhere. Services, config manager, NET START, etc.
It's changing the service credentials that must only be done from config manager because config manager knows what permissions must be set on the new service account.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 23, 2012 at 6:45 am
Hi Gila,
Correct me if i am wrong, SQL Server Configuration Manager would be checkpointed by CheckPoint Manager in Failover clustering. so will it be a point to consider in case of any modification in configuration?
July 23, 2012 at 7:01 am
Thanks everyone.
cheers
July 23, 2012 at 7:05 am
MickyD (7/23/2012)
Hi everyoneCan anyone tell me , or point me to any documentation that states why SQL 2008 services should be stopped and started from SQL Server Configuration Manager ?
Sure I have read \ seen something that says MS recommend doing from here as opposed to services window.
many thanks for any tips \ thoughts on the above.
cheers
I believe when you stop/start from Configuration manager, you are directly hitting the SQL Server engine. It's not recommened to re-start SQL from SSMS since it's a client tool and it might not stop/start properly. So, I would say best practice is to stop/start SQL from Configuration Manager.
Regards,
TA
Regards,
SQLisAwe5oMe.
July 23, 2012 at 7:18 am
SQLCrazyCertified (7/23/2012)
So, I would say best practice is to stop/start SQL from Configuration Manager.
Or failover cluster manager if it's a clustered instance of SQL Server
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 23, 2012 at 7:44 am
SQLCrazyCertified (7/23/2012)
So, I would say best practice is to stop/start SQL from Configuration Manager.
Nope. You can stop/start SQL from config manager, NET commands, client app (eg SSMS), services, etc with no concerns.
Only time there is a recommended route to stop/start is when it's a clustered instance and in that case you should use cluster admin. For a standalone instance there is no preference as to how you stop and start it.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 23, 2012 at 7:45 am
dbasql79 (7/23/2012)
Correct me if i am wrong, SQL Server Configuration Manager would be checkpointed by CheckPoint Manager in Failover clustering. so will it be a point to consider in case of any modification in configuration?
Don't understand.
Changing the service config (eg account) is best done from Config manager. Starting and stopping can be done from anywhere.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 23, 2012 at 8:11 am
GilaMonster (7/23/2012)
Only time there is a recommended route to stop/start is when it's a clustered instance and in that case you should use cluster admin.
And if you don't, Bad Things Happen<tm>. (so says Experience).
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply