All is in the title.

Microsoft are saying everywhere (included Books Online) that a SQL Server
Cluster needs a domain account for the startup account
During the setup process, there is no way to choose a local account.
if, you do, there is an error saying that you have to choose a domain
account instead of a local account.
Fine.
However, after the install, if you go and modify the startup account and
replace it with a local account everything is working perfectly.
I tried it and I could fail over and back without any problem.

I am missing something here.
So the question is:

What's the need for SQL Server startup account to be a domain account?

Thanks
Med Bouchenafa

I have not found that the a domain account is needed, however, in practice, I
think that you will find most shops use the domain account because group
policy settings can be applied. Also, it's only one account, where as if you
use local accounts, they need to be maintained at each server.

HTH,

DetRich

"Med Bouchenafa" wrote:

Also, if the SQL Server service runs as a domain account it simplifies
issues such as accessing network resources, other servers, and so forth.
The account can be granted the needed rights to those resources.

RLF

"DetRich" <DetRich (AT) discussions (DOT) microsoft.com> wrote

SQL clustering uses local binaries but unified storate. In order to
consistently grant permissions to the datbase file objects, the service
accounts need to be domain-level accounts. IT may be OK with the feture set
you are using but to work predictibly across all feature matrix
implementations, domain accounts are essential.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Med Bouchenafa" <com.hotmail@bouchenafa> wrote