granting privilages similar to existing user

I need to grant privilages to a user that are like the privilages of an
existing user. How can I do this?
chuck t.The easiest way would be to write a little SQL-DMO script. Create a user
object and then execute the ListObjectPermissions method. Alternatively,
you can use the Script method and replace the old user with the new user.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada tom@.cips.ca
www.pinpub.com
"Chuck" <Chuck@.discussions.microsoft.com> wrote in message
news:335EB4BA-1BCF-4151-9446-5D4BCA569657@.microsoft.com...
>I need to grant privilages to a user that are like the privilages of an
> existing user. How can I do this?
> --
> chuck t.|||Hi,
please check this if it help you to get list :
http://www.sql-server-performance.c...?TOPIC_ID=10504
:-)
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Chuck" wrote:

> I need to grant privilages to a user that are like the privilages of an
> existing user. How can I do this?
> --
> chuck t.

grant permission to all objects

hi,
how should i grant permission to all objects in a database for an
existing user.
R.Kalaivanan
Kalaivanan.
It really depends on what the permissions are. Using the inbuild database
roles is my first stop, and if you are essentially wanting to grant all
permissions on existing objects, then the db_owner role would be useful. If
you wanted a subset of that, then the other roles might be useful (eg
db_datareader) along with schema permissions eg to execute all stored
procedures.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Adding to Paul's comments, if you DO NOT want the user to have permission to
change anything about the tables, views, stored procedures, etc., then
db_owner most likely isn't the best choice. You may need to create your own
database role, giving it the permissions that are required.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uunE5ez1GHA.1252@.TK2MSFTNGP04.phx.gbl...
> It really depends on what the permissions are. Using the inbuild database
> roles is my first stop, and if you are essentially wanting to grant all
> permissions on existing objects, then the db_owner role would be useful.
> If you wanted a subset of that, then the other roles might be useful (eg
> db_datareader) along with schema permissions eg to execute all stored
> procedures.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>

grant permission to all objects

hi,
how should i grant permission to all objects in a database for an
existing user.
R.Kalaivanan
Kalaivanan.It really depends on what the permissions are. Using the inbuild database
roles is my first stop, and if you are essentially wanting to grant all
permissions on existing objects, then the db_owner role would be useful. If
you wanted a subset of that, then the other roles might be useful (eg
db_datareader) along with schema permissions eg to execute all stored
procedures.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com|||Adding to Paul's comments, if you DO NOT want the user to have permission to
change anything about the tables, views, stored procedures, etc., then
db_owner most likely isn't the best choice. You may need to create your own
database role, giving it the permissions that are required.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uunE5ez1GHA.1252@.TK2MSFTNGP04.phx.gbl...
> It really depends on what the permissions are. Using the inbuild database
> roles is my first stop, and if you are essentially wanting to grant all
> permissions on existing objects, then the db_owner role would be useful.
> If you wanted a subset of that, then the other roles might be useful (eg
> db_datareader) along with schema permissions eg to execute all stored
> procedures.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>