June 21, 2012 at 12:59 pm
SQLServer 2005 SP3
I had a request for one particular user to have almost blanket permission across 10+ databases on the same instance.
Database roles and user were created for each database and the user was added to the role. It works fine expect one database is reporting the error message above.
The login looks ok, except this database is unchecked. Checking it does nothing as it is instantly reverted upon closing out the GUI.
The database reports no orphaned users.
Additionally, ALTER user WITH login accomplished nothing.
Any thoughts?
June 21, 2012 at 1:07 pm
Your heading is the entire error message? Doesn't tell me a thing, sorry.
June 21, 2012 at 1:13 pm
jshurak (6/21/2012)
The login looks ok, except this database is unchecked. Checking it does nothing as it is instantly reverted upon closing out the GUI....
Any thoughts?
Just a basics check. The login you're using to set this user's permission is SA on the server that the database resides on, correct? Does the SA level login you're using have explicit DENY rights against the database to not allow it to adjust security? Is the database in read only mode, suspect, or have any other odd setting? Does the person in question belong to an AD group that is explicitly denied to that database?
There's a lot of intricacy to explore, you'll need to start with yourself and make sure you can set permissions to that database with whatever login you're using and work down from there.
As to the error message... I can't help you with that one, I'd need the full one, but that doesn't sound like it's the actual concern.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
June 21, 2012 at 1:41 pm
I have SA rights. Like I said, this works fine in all other databases....
edit: Database appears to be identical in options, etc as all the other databases.
Here is the error message
The server principal login is not able to access the database dbname under the current security context.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply