INF: SQL Access Permissions and Trigger Execution

Last reviewed: April 25, 1997
Article ID: Q47270

The information in this article applies to:

  - Microsoft SQL Server version 4.2 for OS/2

SUMMARY

The following information discusses the topic of access permissions and trigger execution.

MORE INFORMATION

If an operation on an object causes an implicit operation on another object, and both objects have the same owner, it is assumed that all privileges granted for the explicit operation also apply to the implicit operation. If the objects have different owners, it is assumed that the different owners may have different ideas about who should be granted access to what.

If user U1 owns table T1, and that table has a trigger that accesses table T2 owned by user U2, then a third user U3 must have explicit permission to access tables T1 and T2. If user U1 had also owned T2, then user U3 would require only explicit permission to use T1.

Triggers should not provide a way for someone other than the owner of an object to determine who has access.

In a production environment, all objects should be owned by the DBA and this is not a problem. In a free-for-all environment, with many users creating objects and triggers, this is the only way to provide security.


Additional query words: Transact-SQL permissions
Keywords : kbusage SSrvServer
Version : 4.2 4.2a 4.2b
Platform : OS/2


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.