Databases
StackOverflow2013
Postsdbo
POSQL Server: How to permission schemas?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL Server: How to permission schemas?
    primarykey
    data
    text
    <p>Inspired by various schema related questions I've seen...</p> <p><a href="http://msdn.microsoft.com/en-us/library/ms188676.aspx" rel="noreferrer">Ownership chaining</a> allows me to GRANT EXECUTE on a stored procedure without explicit permissions on tables I use, if both stored procedure and tables are in the same schema.</p> <p>If we use separate schemas then I'd have to explicitly GRANT XXX on the the different-schema tables. The ownership chaining example demonstrates that. This means the stored proc executing user can read/write your tables directly.</p> <p>This would be like having direct access to your instance variables in a class, bypassing getter/setters, breaking encapsulation.</p> <p>We also use row level security to restrict what someone sees and we apply this in the stored procedures.</p> <p>So, how can we maintain schema separation and prevent direct table access? </p> <p>Of course, the question won't apply if you use an ORM or don't use stored procs. But I'm <em>not</em> asking if I should use an ORM or stored proc in case anyone feels the need to enlighten me...</p> <p>Edit, example</p> <pre><code>CREATE USER OwnsMultiSchema WITHOUT LOGIN GO CREATE SCHEMA MultiSchema1 AUTHORIZATION OwnsMultiSchema GO CREATE SCHEMA MultiSchema2 AUTHORIZATION OwnsMultiSchema GO CREATE USER OwnsOtherSchema WITHOUT LOGIN GO CREATE SCHEMA OtherSchema AUTHORIZATION OwnsOtherSchema GO CREATE TABLE MultiSchema1.T1 (foo int) GO CREATE TABLE MultiSchema2.T2 (foo int) GO CREATE TABLE OtherSchema.TA (foo int) GO CREATE PROC MultiSchema1.P1 AS SELECT * FROM MultiSchema1.T1 SELECT * FROM MultiSchema2.T2 SELECT * FROM OtherSchema.TA Go EXEC AS USER = 'OwnsMultiSchema' GO --gives error on OtherSchema EXEC MultiSchema1.P1 GO REVERT GO CREATE PROC OtherSchema.PA AS SELECT * FROM MultiSchema1.T1 SELECT * FROM MultiSchema2.T2 SELECT * FROM OtherSchema.TA Go GRANT EXEC ON OtherSchema.PA TO OwnsMultiSchema GO EXEC AS USER = 'OwnsMultiSchema' GO --works EXEC OtherSchema.PA GO REVERT GO </code></pre> <p>Edit 2:</p> <ul> <li>We don't use "cross database ownership chaining"</li> <li>Row level security is a red herring and irrelevant: we don't use it everywhere</li> </ul>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USgbn
    1. USgbn
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSQL Server: How to permission schemas?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSQL Server: How to permission schemas?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSQL Server: How to permission schemas?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWould it be possible to provide a coded example of the seperate schema scenario you are describing for clarity please? In your scenario, do the two seperate schemas have the same owner?
      singulars
      1. POSQL Server: How to permission schemas?
      1. USJohn Sansom
    2. COWhy vote close for serverfault? It's for code monkeys, not sysadmins...
      singulars
      1. POSQL Server: How to permission schemas?
      1. USgbn
    3. CO@John Sansom: yes I will.
      singulars
      1. POSQL Server: How to permission schemas?
      1. USgbn
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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