Re: Thank you very much...again

From: Jason Tai (jastai@hotmail.com)
Date: 07/22/02


From: "Jason Tai" <jastai@hotmail.com>
Date: Mon, 22 Jul 2002 13:39:21 -0700


You are right. The reason that we need to grant
permissinos to a database user to two tables in tempdb is
because of a ASP.NET application. The user who needs to
access that application needs to have the select,
delete..etc permissions on tempdb. We are not using the
guest account for this due to the security concerns.

You have really been a great help to me and I want to
thank you for all your help.

Jason
>-----Original Message-----
>I've lost track of the reasons for this but the guest
acount
>exists in tempdb so all users have access to tempdb
through
>the guest account.
>Tempdb is meant for more of a temporary work area so I'm
not
>sure what permissions need to be granted but if this
>involves objects and such, they may be better off in
another
>database which would avoid some of this.
>
>-Sue
>
>On Mon, 22 Jul 2002 11:40:34 -0700, "Jason Tai"
><jastai@hotmail.com> wrote:
>
>>Hi! Sue:
>>
>>I eventually got it to work! However there are some
>>things I did not do exactly what you specified because
of
>>the following reason
>>
>>* It is impossible (at least according to the syntax
>>check) to grant permissions from one database to
>>another. As a result, the grant select on tempdb will
>>not work if the store procedure is in master database.
>>
>>The way I did it is to create the store procedure in
the
>>model database so tempdb will have that store procedure
>>everytime the server restarts. After that I created a
>>store procedure in Master Database to call the store
>>procedure everytime the server restarts. It worked
that
>>way.
>>
>>If you have an alternative please let me know. Thanks.
>>
>>Jason
>>>-----Original Message-----
>>>Jason,
>>>Yes...you can include the grant statements in the
stored
>>>procedure, e.g.
>>>grant select on tempdb..SomeTable to SomeUser
>>>Also, you don't have to start a new message when you
>>have a
>>>follow up question on a reply. You can just reply to
the
>>>response you received and then it keeps all the follow-
up
>>>messages and postings on the topic together in one
>>thread.
>>>
>>>-Sue
>>>
>>>On Mon, 22 Jul 2002 09:33:57 -0700, "Jason Tai"
>>><jastai@hotmail.com> wrote:
>>>
>>>>Hi! Sue:
>>>>
>>>>Thanks a lot! It worked. However I need to grant
>>>>permissions to the users on two tables. Can I
include
>>>>that in the store procedures? (i.e. They reference
to
>>>>the same database - tempdb). Thanks again for your
>>help.
>>>>
>>>>Jason
>>>
>>>.
>>>
>
>.
>



Relevant Pages

  • RE: user permissions in a database as a whole or tables
    ... user permissions in a database as a whole or tables ... The way to give permissions to a user is a simple GRANT. ...
    (comp.databases.informix)
  • Re: user permissions in a database as a whole or tables
    ... like PDF better but that was not helping this time either. ... user permissions in a database as a whole or tables ... The way to give permissions to a user is a simple GRANT. ...
    (comp.databases.informix)
  • Re: SQL Server 2005 Stored Procedure security annoyances
    ... stored proecedure on a database wide level? ... GRANT EXECUTE ON SCHEMA::MySchema TO MyRole ... I am sure I will forget some SP's and probably forget to set the rights ... permissions because not all stored procedures are equal. ...
    (microsoft.public.sqlserver.security)
  • Re: Relation of OS user to Informix database user
    ... I created two operating system users, say A and B, gave both GRANT CONNECT and GRANT RESOURCE permissions from the informix DBA user. ... When you created the database, was a MODE ANSI database, or a logged or an unlogged database. ... REVOKE SELECT ON TABLE T FROM B. This gave an error saying no record in ISAM and Unable to revoke permissions. ...
    (comp.databases.informix)
  • Re: Oracle permissions issue Oracle 9.2.0.7/Win 2003
    ... We are being dinged for grants that any schema owner is ... giving on its objects to database roles. ... SYSTEM user or a user with DBA privileges should grant the permissions ...
    (comp.databases.oracle.server)