quote:In the end I dumped the application role and harassed the developer to change his code. If there were a way to “undo” or roll back the application role setting, this would not have been a problem.
I agree wholeheartedly. While a simple stored procedure can reset client settings, nothing exists to reset an app role back to the base user. Not sure why as it would make resource pooling more friendly.
quote: I'll try and be fair and balanced in this article, but I've provided this disclaimer in case I'm not.
Funny you mentioned that. I read the judge's comments and I don't think my article could in any way be construed with O'Reilly so I think I'm safe. If not, us DBAs aren't exactly full of money so it's like trying to squeeze blood out of a turnip.
Jul 13
We're thinking of using application roles, but I don't quite get how to give it permissions. We currently have a sql login that's being used & abused. It has dbo access, and I want to use an app role that also has dbo access so that it can create work tables via an application. I can see how to grant access to specific tables and SPs, but I don't want to have to manually manage specific objects.
What am I missing ?
