Re: SQL account rights
- From: "Warren Brunk" <wbrunk@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 4 Oct 2006 14:46:00 -0700
the short answer to your question is NO WAY. The SQL Server account does not
need to be a member of the Domain Admins. Is it not a good practice for a
SQL Server account to be a domain admin. It increases surface area
significantly.
Here is a list of account that can run your services...
http://support.microsoft.com/kb/907557
Perhaps you should make it a regular user on the domain but a local
administrator on the SQL Server boxes.
There are a million ways to set up security for your SQL Server box and
using a domain administrator isnt a good pratice.
You can even use a new feature called User Instances
http://msdn2.microsoft.com/en-us/library/ms143684.aspx
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Lenny" <Lenny@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BEAA37AD-C376-41F7-B4D3-843F7F2C8D51@xxxxxxxxxxxxxxxx
Hi,
In our SQL 2000 environment, we have an account called SQLEXEC, which is a
domain account (Windows account, therefore). We use it to install, set
up,
configure all SQL server functions. My question:
Are there any SQL related functions that really require us to assign this
account to Domain Admin group in our Windows 2003 domain environment.
We prefer not to since domain admin has a lot of power.
Please advise.
Thanks.
Lenny
.
- Follow-Ups:
- Re: SQL account rights
- From: A McGuire
- Re: SQL account rights
- Prev by Date: Re: remote Local user account permissions to SQL 2000 SP4 server
- Next by Date: Re: SQL account right issues
- Previous by thread: Re: Linked Server Confusion - I don't know where to start...
- Next by thread: Re: SQL account rights
- Index(es):
Relevant Pages
|
Loading