Re: Restricting Access to BUILTIN\Administrators
From: Mark J. McGinty (mmcginty_at_spamfromyou.com)
Date: 06/22/05
- Next message: Michael D. McGill: "SQL Server Error 18452"
- Previous message: Hari Prasad: "Re: securing mdf files"
- In reply to: BC DBA: "Restricting Access to BUILTIN\Administrators"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 22 Jun 2005 09:00:34 -0700
"BC DBA" <BCDBA@discussions.microsoft.com> wrote in message
news:E7A2AE6A-971A-434C-B2B0-FC33419DA356@microsoft.com...
> 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'.
You need to change the database owner (by calling sp_changedbowner) for each
database first, then remove the builtin group from the sysadmin role.
> 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.
If the domain user in this case is one of the ones for which you want to
restrict SQL access, this change will do that, they won't have access
anymore. If the domain user is one that will be added to the SQL admin
group, access will be granted via role membership, so no harm no foul.
Be sure that the default db is valid for the ones that will have access,
because if it isn't they won't be able to login -- master is always a safe
choice.
-Mark
- Next message: Michael D. McGill: "SQL Server Error 18452"
- Previous message: Hari Prasad: "Re: securing mdf files"
- In reply to: BC DBA: "Restricting Access to BUILTIN\Administrators"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
