Controlling activation of SPROCs

  • Is there anyway I can set MS SQL Server stored procedures so that they can only be activated by another stored procedure and can not be activated by an outside system call? 

  • By outside system call, do you mean a front end application?  And if so, does this front end application call some stored procedures and you are trying to restrict access to others?

    I must admit, I have never used them, but an application role may be able to do what you need?  Others may be able to tell you whether an application role will fit your needs...

  • Assume all SPs are owned by dbo.  You deny execute permissions to all users for those procedures you want to protect.  Only other dbo. procedures then can call them.

    More usually, I do this the other way round - users only have execute access to stored procedures and no access of any type to tables.  All table access then is rigidly controlled through my SPs.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply