Databases
StackOverflow2013
Postsdbo
POSQL Permissions / Securables - Can I give permissions to a "Select" from a View that uses another View that doesn't have permission granted?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL Permissions / Securables - Can I give permissions to a "Select" from a View that uses another View that doesn't have permission granted?
    text
    copied!<p>Here's my scenario...</p> <p><strong>SQL Role</strong></p> <ul> <li>Staff_User</li> </ul> <p><strong>Scheme</strong></p> <ul> <li>People</li> </ul> <p><strong>Tables</strong></p> <ul> <li><p>People.Persons</p></li> <li><p>People.PhoneNumbers</p></li> </ul> <p><strong>Views</strong></p> <ul> <li><p>People.vtPersons - <em>The vtPersons view filters the data from the Persons table showing only that which belongs to the currently logged in user.</em></p></li> <li><p>People.vtPhoneNumbers - <em>The vtPhoneNumbers view filters the data from the PhoneNumbers table showing only that which belongs to the currently logged in user.</em></p></li> <li><p>People.vwContactInformation - <em>The vwContactInformation "View" combines the data from vtPersons and vtPhoneNumbers so it can be used as a query in a Crystal Report.</em></p></li> </ul> <p>The Staff_User role has been granted "SELECT" permission to the vwContactInformation view and nothing else.</p> <p>I am getting an error now saying that permission is denied to the object vtPhoneNumbers. Must I also grant "SELECT" permission to this view? From experience in another SCHEME I did NOT have to do this and everything worked well. But now I'm getting this error in a second SCHEME that I've created. Can anybody suggest what I have in the first scheme that allows the permissions to cascade to views, tables, functions etc that are called from the view made accessible to the role.</p> <p>Thanks, Justin</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload