RE: Restricting Access to BUILTIN\Administrators

From: Alejandro Mesa (AlejandroMesa_at_discussions.microsoft.com)
Date: 06/22/05


Date: Wed, 22 Jun 2005 07:53:40 -0700

See if this helps:

SQL Server Security: Security Admins
http://www.sqlservercentral.com/columnists/bkelley/sqlserversecuritysecurityadmins.asp

Removing the Builtin Administrators - Some Pitfalls to Avoid
http://www.sqlservercentral.com/columnists/kKellenberger/removingthebuiltinadministratorssomepitfallstoavoi.asp

AMB

"BC DBA" wrote:

> I have a bunch of SQL servers (2000, and 7) that I inherited when I took over
> as the DBA in my organisation. Due to decisions outside my control there are
> a number of users that have been granted Domain Admin rights which
> automatically grants them sa privileges to the SQL Servers via
> BUILTIN\Administrators.
>
> Legislation requires us to restrict access to data to those individuals that
> require access, so I need to prevent members of the Domain Administrators
> group access to the servers.
>
> What I thought I could do was to create another Domain Group say SQL Server
> Administrators. Grant that the System Administrator role to the NT Group and
> then Deny Login to the BUILTIN group. See the problem? If you are a member of
> both accounts then you are denied access (Deny supercedes Grant).
>
> Next thought remove the BUILTIN group from the System Administrators Role
> and remove access to each of the databases on the server. Problem is that it
> has database owner ticked for each database in EM and when I remove that I
> get the following
>
> Error 15405: Cannot use the reserved user or role name 'dbo'.
>
> Looking at one of the databases my domain user is the owner and there is no
> other user so I don't think that changing the dbo for each of the databases
> will help. Anyone any other ideas (I have thought about removing the users
> from the Domain Admins group but I would upset a lot of people)
>
> --
> Regards
>
> Tony



Relevant Pages

  • Re: Database ownership best practice
    ... by a domain user, or a SQL Server login, if that user leaves you have to ... Mike Epprecht, Microsoft SQL Server MVP ... > administrators and some others. ... > make an NT administrator the owner of all databases, ...
    (microsoft.public.sqlserver.security)
  • Re: why>?
    ... On your desktop-- you'll be running SQL Server behind the scenes. ... it isn't risky to allow end users to create databases. ... it is no more risky than giving you the ability to create spreadsheets. ... I'm not saying that Oracle and IBM are going away. ...
    (microsoft.public.excel)
  • Re: Please answer my queries for fresh Installation
    ... Moving SQL Server Databases ... Using WITH MOVE in a Restore to a New Location with Detach/Attach ... Disaster Recovery Articles for SQL Server ...
    (microsoft.public.sqlserver.server)
  • Re: Please answer my queries for fresh Installation
    ... You can restore MSDB as well as master. ... > SQL Server, It will create Master, MSDB databases. ...
    (microsoft.public.sqlserver.server)
  • Re: Moving SQL Server 2000 from NT4.0 to Windows 2003
    ... Detach your existing user databases, ... user databases (or RESTORE) to the new server. ... > Hey Steve, ... Windows 2003 will not allow SQL Server SP less than 3. ...
    (microsoft.public.sqlserver.server)