Re: object reference in stored proc
From: Jim Stallings (anonymous_at_discussions.microsoft.com)
Date: 04/01/04
- Next message: Sue Hoegemeier: "Re: losing permisions in tempdb"
- Previous message: J C: "granting permission"
- In reply to: Andrew J. Kelly: "Re: object reference in stoed proc"
- Next in thread: Andrew J. Kelly: "Re: object reference in stored proc"
- Reply: Andrew J. Kelly: "Re: object reference in stored proc"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 1 Apr 2004 09:36:16 -0800
Hi Andrew,
Thanks for taking the time to reply and the article you pointed me to was very useful. However, I may be missing something in reading the article. This seems to apply to the stored procedure declarations which we are already qualifying with owner name. What we are discussing is whether there is a problem with user security setup and the table reference "within" the stored procedure.
The basic question was:
Is there any reason for security purposes to qualify the tables being accessed in a stored procedure with the owner name. All of our stored procs and tables are created with dbo ownership. While some of our tables may be in other databases, all stored procs are in a single database and use views (also dbo owner) to access these tables. We will set up a single application user with the public role and grant execute to public for all stored procs.
With this configuration is it ever necessary to qualify the table(s) being referenced in a stored procedure with the owner name?
Jim
- Next message: Sue Hoegemeier: "Re: losing permisions in tempdb"
- Previous message: J C: "granting permission"
- In reply to: Andrew J. Kelly: "Re: object reference in stoed proc"
- Next in thread: Andrew J. Kelly: "Re: object reference in stored proc"
- Reply: Andrew J. Kelly: "Re: object reference in stored proc"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|