Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
andyjaar
Starting Member
8 Posts |
 Posted - 2005-02-15 : 09:33:28
|
| Hi,I am currently using SQL Server 7.I understand the concept of referential integrity, but am confused as to exactly what the "DRI" option on the Permissions screen within Enterprise Manager actually does? It doesn't seem to make a difference as to whether it enforces the rules or not (thankfully in my case). As I understand it the CASCADE option has only come in for SQL Server 2000, so it cant mean whether or not the CASCADE would be triggered by that user. I would appreciate someone telling me what it does as the "Administrators Companion" book I have just informs me that it is there and that I can tick it, no mention of what it actually does. ThanksAndy Hall. |
|
|
hgorijal
Constraint Violating Yak Guru
277 Posts |
Posted - 2005-02-16 : 06:03:59
|
| For most purposes, RI and DRI are both synonyms.RI is of two types :1. DRI (Declarative Referential Integrity) : Where, data integrity is maintained by a set of declared rules (or referential constraints) defined in CREATE or ALTER tables statements.2. PDI (Procedural Data Integrity) or RAI (Referential Action Integrity) : Which enforces data integrity thru ,mostly, triggers, and also views and stored procedures.The DRI option in EM is to GRANT, REVOKE or DENY the ability to define RI constaints in CREATE or ALTER table statements.hthHemanth GorijalaExchange a Dollar, we still have ONE each._______Exchange an Idea, we both have TWO each. |
 |
|
|
andyjaar
Starting Member
8 Posts |
Posted - 2005-02-16 : 07:41:23
|
| So it would only be relevant for a user that has CREATE TABLE/ALTER TABLE access?If they do then you can use it to ensure they cannot make RI rules involving certain tables?Thanks makes sense, thanks for your help. |
|
|
|
|
|
|
|
|
DRI in Enterprise Manager Permissions