Re: DROP Statement
From: Sue Hoegemeier (Sue_H@nomail.please)
Date: 07/17/02
- Next message: Kalle Dahlberg: "Removed BUILTIN/Administrators from sysadmins - reinstall?"
- Previous message: MCLTECH: "Re: eliminate an Internet connected Interface"
- In reply to: Rich: "DROP Statement"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Sue Hoegemeier <Sue_H@nomail.please> Date: Wed, 17 Jul 2002 07:17:23 -0600
Some of the create permissions are transferrable but alter
permissions are not. The list of create statement
permissions you can grant can be found in the books online
topic:
Managing Permissions
For a user to create the objects as being owned by dbo, the
user needs to be the database owner, a member of sysadmins
or a member of db_ddladmin. Membership in these roles would
allow dropping objects. For user who are not members of
these groups, the database owner, sysadmins, db_ddladmins
and db_securityadmins can change the object ownership using
sp_changeobjectowner.
-Sue
On Wed, 17 Jul 2002 12:06:20 +0100, "Rich"
<richbrownesq@hotmail.com> wrote:
>Hi,
>
>Is it possible to allow permissions to the CREATE and ALTER statements but
>not DROP. I can use the db_ddladmin role but this allows the user to DROP
>objects. Ideally i want the user to be able to create objects as dbo too.
>
>Thanks
>Rich
>
- Next message: Kalle Dahlberg: "Removed BUILTIN/Administrators from sysadmins - reinstall?"
- Previous message: MCLTECH: "Re: eliminate an Internet connected Interface"
- In reply to: Rich: "DROP Statement"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
