Re: Grant permissions

From: Arun (arunkkk_at_yahoo.com)
Date: 09/28/03


Date: Sun, 28 Sep 2003 02:33:07 -0700


This is actually for deployment of a web application, so I
would be doing this whole exercise only once
Thanks

>-----Original Message-----
>A better solution is to create a role that has
permissions to execute
>all the stored procedures in the database, and just add
the user to
>the role. That way when the situation arises in the
future you'll just
>need to add a new user to that role, which is one line of
code.
>
>-- Mary
>MCW Technologies
>http://www.mcwtech.com
>
>On Wed, 24 Sep 2003 00:22:20 -0700, "Arun"
<arunkkk@yahoo.com> wrote:
>
>>Can I grant execute permission to all stored procedures
in
>>a database to an user in a single statement
>>
>>grant execute on all to <user name> doesn't work !
>
>.
>



Relevant Pages

  • Re: Database Model - Class, objects and interaction
    ... I was just proving stored procedures can call views. ... stuff like security and logging. ... So given 100,000 users, you would create database accounts for each? ... Part of our system's integrity was its reliability, and reliability is often assisted by simplicity. ...
    (comp.object)
  • Re: Database Model - Class, objects and interaction
    ... Stored procedures should only be used as a last resort if you cant use ... I've not said that views shouldn't be created, only that they shouldn't be exposed as the interface to the database. ... But business rules can be more complicated than simply defining overdue invoices. ...
    (comp.object)
  • Re: Infinite Loops and Explicit Exits
    ... the whole payroll system would be dependent on proper database ... I design large systems the same way. ... Stored procedures ARE application code. ... any language, including Cobol. ...
    (comp.lang.cobol)
  • Re: Identity Column
    ... the end use is using Crystal Reports - where is the magic? ... The user will connect using Active Directory from their desktop to the database server or do please explain the magic.... ... Using stored procedures you permission on the stored proc only; the user can only execute the stored procedure with the parameters defined, there is no select * from to get all the information in your database. ...
    (microsoft.public.sqlserver.programming)
  • Re: Infinite Loops and Explicit Exits
    ... The behaviour could only be changed by changing the database. ... >>designing proper databases and using stored procedures on them, ... are database dependent and not available in COBOL. ... But with extended SQL you simply write the procedures in SQL ...
    (comp.lang.cobol)