I need that the user does not have access to another scheme, but the stored procedure could access a different schema.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I need that the user does not have access to another scheme, but the stored procedure could access a different schema.
What you are describing is not possible.
If
b.procedurecan select, insert, update or delete ona.table, then anyone logged in asbcould do so too.What you should do instead is create procedure
a.procedureandgrant execute on a.procedure to b.