Sybase Technical Library - Product Manuals Home
[Search Forms] [Previous Section with Hits] [Next Section with Hits] [Clear Search] Expand Search
Renaming stored procedures [Table of Contents] Dropping stored procedures

Transact-SQL User's Guide

[-] Chapter 14 Using Stored Procedures
[-] Using stored procedures as security mechanisms

Using stored procedures as security mechanisms

You can use stored procedures as security mechanisms to control access to information in tables and to control the ability to perform data modification. For example, you can deny other users permission to use the select command on a table that you own and create a stored procedure that allows them to see only certain rows or certain columns. You can also use stored procedures to limit update, delete, or insert statements.

The person who owns the stored procedure must own the table or view used in the procedure. Not even a System Administrator can create a stored procedure to perform operations on another user's tables, if the System Administrator has not been granted permissions on those tables.

For information about granting and revoking permissions of stored procedures and other database objects, see the System Administration Guide.

Renaming stored procedures [Table of Contents] Dropping stored procedures