Re: database owner

As long as the backupexec Windows account is a member of the Windows Administrators group, it can access the SQL Server as a sysadmin role member by default.


--
Hope this helps.

Dan Guzman
SQL Server MVP

"Andy.I" <Andy.I@xxxxxxxxxxxxxxxx> wrote in message news:1218DD35-26E0-4B87-910E-B8298D84BCFD@xxxxxxxxxxxxxxxx
Thanks for the reply.

And I don't have to make an own login for the backupexec account on the database, as long as it is a member of the dedicated admins group I made on the database that are a part of the system administrator role?

/A
"Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:8AA3B158-A46C-44FD-8F14-7D7F548786CF@xxxxxxxxxxxxxxxx
Are there any necessary steps I should take or correct this setup? (I hope this explanation was understandable)

Having the backupexec account probably won't do any harm as long as the Windows account exists. To ensure a database owner is never orphaned, I use 'sa' as the database owner unless I have a reason to do otherwise. You can use sp_changedbowner to specify the desired owner. For example:

USE MyRestoredDatabase
EXEC sp_changedbowner 'sa'
GO

--
Hope this helps.

Dan Guzman
SQL Server MVP

"Andy.I" <Andy.I@xxxxxxxxxxxxxxxx> wrote in message news:5B2D9624-7F22-4AA4-AB1B-F48C01F180DC@xxxxxxxxxxxxxxxx
Hi

I have recently migrated several databases between 2 SQL server 2K servers, and used backupexec in this process.
Backup from old server, and db restore to new server. Migrated all logins with a stored procedure I found in MS's knowledgebase.
Now on the new server the backupexec user account is database owner on all the migrated databases. I do not have a dedicated login for this user on the server, but this account is member of a administrators group in the sql server and this group is dedicated at dbo on all databases and belongs to the sysadmin servers role. So this way all rights are inherited from the group membership.
My question is, will this create any issues? The way I see it, the sid of the database owner, doesn't exist in the syslogins table in the master DB, and it doesn't exist as an own login in sysusers on the database in question, even if it is a member of the administrators group on the database.
I use SQL Server 2000 Sp4 with mixed security.

Are there any necessary steps I should take or correct this setup? (I hope this explanation was understandable)

/A



.

Relevant Pages

  • Re: database owner
    ... Thanks for all your help Dan, ... it can access the SQL Server as a sysadmin role member by default. ... And I don't have to make an own login for the backupexec account on the database, as long as it is a member of the dedicated admins group I made on the database that are a part of the system administrator role? ... I do not have a dedicated login for this user on the server, but this account is member of a administrators group in the sql server and this group is dedicated at dbo on all databases and belongs to the sysadmin servers role. ...
    (microsoft.public.sqlserver.security)
  • Re: Roles in Roles
    ... For a database user it is easy to find the database roles the user is a ... role is a member of. ... On SQL 2005 permissions is more intricate than ever, ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (microsoft.public.sqlserver.security)
  • Re: Adding permissions to an AD user on a remote database
    ... not if it's a member of a database role. ... "Indicates whether the current user is a member of the specified Microsoft ... Windows group or Microsoft SQL Server database role. ...
    (microsoft.public.sqlserver.security)
  • Re: Adding permissions to an AD user on a remote database
    ... "Indicates whether the current user is a member of the specified Microsoft ... Windows group or Microsoft SQL Server database role. ...
    (microsoft.public.sqlserver.security)
  • Re: Trusted connection
    ... If you is a member of domain admin so you probably is ... Admistrators group or any group that has an access to SQL Server ... > user account) which is added to a domain? ... > local Administrators group but the ...
    (microsoft.public.sqlserver.security)