How many people actually create accounts for the SQL
Server services to use? I would expect that once you step out of the enterprise
the majority wouldn't be. Even though its bet practice.
Why do I think that? Because its generally a pain. If installing the full
suite, you have the engine, analysis services, reporting services, integration
services, the browser and sql agent all needing service accounts.
So thats 6 accounts, you then need to assign the relevant service to the
relevant group.
Then you need to add the SQL Agent user access to the SQL Server.
So what do people do, I suspect most either, use their own account (which is
likely to be a domain account and/or a local admin), the local admin account,
the network service and the local system account. None of which follow the
principle of running with least priviledges.
That results in lots of setups that are running with high elevated
priviledges and/or situations where the network or local system accounts have
ben used which result in certian features not working, and thus casing confusion
and annoyance.
Since the setup fr SQL has change in CTP5 and the service account selection
is very different some MVPs have been discussing the options. Hugo Kornelis came
up with a great idea. Why doesn't setup create the accounts for us. I remember
IIS used to do that to avoid a highly priviledge uer being used as the default
IIS account. So why can't SQL.
Here is Hugo's suggestion on conect, https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=310609.
If you think its a good idea please vote. Even though the item is still closed,
if we get enough votes MS should reconsider it.