January 22, 2009 at 11:54 am
This is an odd one. Wasn't sure which forum to put it in.
We have a DB role called ReadOnly which has execute permissions on Schema dbo. We have a specific domain user (UserX) which belongs to this role. Everything seems happy. UserX can execute any proc or function in the dbo schema.
Until a new proc gets put into the database. Then UserX can't even see the new proc until we re-run the execute permission script for ReadOnly.
Has anyone seen this behavior before? Is there a way around it other than having to re-grant the Execute permissions?
Thanks in advance!
January 22, 2009 at 12:42 pm
Is the problem present if the user completely disconnects from SQL Server and reconnects?
K. Brian Kelley
@kbriankelley
January 23, 2009 at 6:09 am
That's a good question. I'll check.
I have a sneaking suspicion, though, that there's something in this scenario that the BU in question isn't telling me. Something outside of SQL Server that might be contributing to the perceived problem.
Thanks, Brian.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply