sql server new users: Service Account -- sql server new users

Service Account

David Veeneman
12/22/2005 4:28:12 PM

sql server new users:

I am installing SQL Server 2005 (Developer Edition) to use with Visual
Studio 2005. I am installing it on my development machine, which is not part
of a domain, and I am going to use it strictly for development, not in
production.

Here is my question: What is the best way to set up the service account(s)
for SQL Server? One account for all SQL Server services using the NETWORK
SERVICE account account looks like the simplest configuration. Is that a
good choice, or are there problems associated with that configuration? What
would be a better way to set up the service account?

Thanks in advance for your help.

David Veeneman
Foresight Systems

Re: Service Account

Mike Hodgson
12/23/2005 12:09:50 PM

I would create a local account on the dev machine (not in local
administrators, just a standard user account) and use that account for
all the services during the setup (the setup routines will automatically
tweak the ACLs & rights in the registry & the filesystem as necessary
for that account).

--
*mike hodgson*
blog: http://sqlnerd.blogspot.com

[quoted text, click to view]

Re: Service Account

Anthony Thomas
12/24/2005 12:36:01 PM

Good points. I would add that you might consider separate local accounts
for each of the core functional service areas: DBEngine (including the
agent), Analysis Services, Integration Services, Reporting Services, and
Notification Services.

Although you could get by with a single account for all of these on a
development platform, many times what you need to test as part of the
solution is the various security issues that may arise in a production
system. Having the separate account allows you to conduct Unit Tests within
the scope of each major area.

Furthermore, in all likelihood, your production environment will have these
various services distributed across multiple servers: thus, the term
Distributed Computing; any other configuration would be tantamount to a
mini-mainframe installation, completely counter-intuitive to what
distributed computing is all about. Your dev/test environment needs to
mimic this behavior as best it can, usually given fewer resources.

Sincerely,

Anthony Thomas

--

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server new users group.