MSSQL: Choice of service accounts
Posted
by
Troels Arvin
on Server Fault
See other posts from Server Fault
or by Troels Arvin
Published on 2011-02-11T22:01:08Z
Indexed on
2011/02/11
23:27 UTC
Read the original article
Hit count: 250
sql-server
When installing MS SQL Server 2008, one needs to associate a service account with the installation (possibly even several accounts, one for the SQL Server Agent, one for Analysis Services, ..., but let's leave that for the case of simplicity). The service account may be local account, or a Windows domain account.
If a domain account is used: Can MSSQL start, if connectivity to the domain controllers is temporarily down? If the answer is yes:
Should each DBMS instance on each server have a separate account, or does it make sense to use a particular "MSSQL" domain account on all MSSQL-installations in the organization?
If separate accounts are used for each instance on each server: Does it make sense to create a special MSSQL security group in the domain and place all the MSSQL service accounts in that group, perhaps to ease replication, etc?
Is there a common, generally accepted naming convention for MSSQL service account(s)?
© Server Fault or respective owner