Documentation / system view ambiguity: An inline tablevalued function is not a signable module - by Robert Heinig II

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 781828 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/21/2013 2:55:51 AM
Access Restriction Public


Some may be surprised by the 15560 message (Cannot add or drop a signature on '%' because only modules can be signed.) in one specific context: Inline tablevalued functions. <br/>

IF's are by their nature not modules but more akin to parametrized views, they have no plan of their own. Therefore it is understandable they cannot be signed and cannot be used for permission isolation. <br/>

However, both sys.sql_modules and the BOL topic for ADD SIGNATURE suggest otherwise. An IF has an entry in sys.sql_modules even though most columns do not apply, and the signing doc does not differentiate the three function types... </br>

I request documentation clarification both in and .
Sign in to post a comment.
Posted by Microsoft on 4/8/2013 at 3:28 PM
Updated the ADD SIGNATURE topic with the statement: Inline table-valued functions cannot be signed.
I decided not to update the sys.modules topic. It didn't seem to fit.
Posted by Microsoft on 3/21/2013 at 3:25 PM
Thank you for submitting this. I'll take a look.