asked
Why are EXECUTE rights required to use a function?
They're exposed in management studio under "Programmability" below Stored Procedures, but aren't functions read-only constructs? What's the rationale for not governing their usage with READ permissions?
The functions are not the "read-only" constructs. True, the functions cannot do certain things, such as using a side-effecting operator, but they may perform some calculations and return either a scalar value or a table. Because the function is considered to perform some action(s), it needs to be executed, and thus, the execute permission is required. A stored procedure may be merely selecting some data, but still nobody questions the necessity of the execute permission to it right? Just my 2 cents.
18 People are following this question.
