declarative referential integrity (DRI)

[Greg Larsen]

From BOL, I understand that DRI permissions means the
following:

Grant, revoke, or deny declarative referential integrity
permissions on thisobject

What I don't understand is exactly how setting this
permission affects any table access. Would someone be
kind enough to show me an example that demonstrates how
setting the DRI permission to grants, revoke, or denies
affects user access? I've tried a couple of different
tests, but haven't been able to determine how this setting
affects any access.

[Joe Celko]

SQL sees the world as either users or administration. The users have
grant/revoke options in their side of the house (DML) and admins have
grant/revoke options in the other side of the house (DCL, DDL).

--CELKO--
===========================
Please post DDL, so that people do not have to guess what the keys,
constraints, Declarative Referential Integrity, datatypes, etc. in your
schema are.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Tibor Karaszi]

Greg,

Say that you want to create a foreign key which referenced tableX. And say that tableX is owned
by someone else. you would need Referenced permissions to do that. (Think about it, when you
references that table, you restrict UPDATE and DELETE on that table.)
REFERENCES is very rarely used, because if you have relations between tables, you most often
have the same owner.

--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver

"Greg Larsen" <greg....@doh.wa.gov> wrote in message
news:0fca01c1f5f0$e5726480$a5e62ecf@tkmsftngxa07...