asked on

SQL 2008 R2 and Service Accounts

Documentation and articles say when installing SQL Server (2012) you must use a service account when installing on an active directory domain controller (Windows Server 2008 R2 Standard). Says that Local System won't work. I've seen one domain controller server where all SQL services were set to Local System. So is this really true and forced by the SQL installer? There are tons of other services on a domain controller that run as Local System. Also noticed that the sql installer forces you to use Local System on the SQL Browser account, even on a domain controller. So is this just good advice to use a service account, or is it really a functionality problem?

This is in a small office 5 to 20 users situation.

ASKER CERTIFIED SOLUTION

David Johnson, CD

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Vitor Montalvão

There are tons of other services on a domain controller that run as Local System.

Local System is an account that is used by many programs so very good for an hacker to install a program that uses Local System to access to your SQL Server so is really not a good idea to use it as Service Account.
I've an article written about the SQL Server Service Accounts. Give it a read to know what options do you have.

Also noticed that the sql installer forces you to use Local System on the SQL Browser account, even on a domain controller.

About the SQL Browser, that's a service only needs by Named Pipes protocol and doesn't have access to any SQL Server instance and that's why you can use Local System.

Qlemo

Vitor, SQL Browser is required as soon as the TCP/IP port is dynamic (and/or unknown). Named Pipes does not need SQL Browser at all.

Vitor Montalvão

Thanks Qlemo.
I went to re read the SQL Browser service article and I guess his need is related to named instances and TCP/IP:

"However, if the SQL Server Browser service is not running, the following connections do not work:

•Any component that tries to connect to a named instance without fully specifying all the parameters (such as the TCP/IP port or named pipe).
•Any component that generates or passes server\instance information that could later be used by other components to reconnect.
•Connecting to a named instance without providing the port number or pipe.
•DAC to a named instance or the default instance if not using TCP/IP port 1433.
•The OLAP redirector service.
•Enumerating servers in SQL Server Management Studio, Enterprise Manager, or Query Analyzer."

AnthonyMCSE

ASKER

Thanks!