Amit Bansal

About Amit Bansal

Amit Bansal is always brainstorming around SQL Server. Despite working with SQL since 1997, he is amazed that he keeps learning new things every single day. SQL Server is AB's first love, and his wife does not mind that. He tries to share as much and spreads the SQL goodness. Internals and Performance Tuning excites him, and also gives him sleepless nights at times, simply because he is not a genius, but quite a hard worker and does not give up. It has been a long and exciting journey since 1997, you can read here: http://sqlmaestros.com/amit-bansal/ He is on Twitter: https://www.twitter.com/A_Bansal

View all posts by Amit Bansal →

6 Comments on “SQL Server user mapping – a strange issue while creating a login”

  1. Old administrator rule come back again. Never use new features in production servers, include services packs 🙂 There’s no first time, when Microsoft lost or in this case add some functionality.

    Nikodem

  2. I just tried to duplicate your issue. I’m not able to. It’s working as expected. Are you running the base release of SP1?

    There are several nasty bugs introduced with SP1, you need to be running CU3 with hotfix KB 2832017 (http://support.microsoft.com/kb/2832017). CU3 with this hotfix is the first “useable” build of SP1.

  3. You may need to check if the user who is creating this user and mapping with the login has required privileges to make DBO user role effective. And yes, the best way is to go through CUI which we are re;uctant when easier GUI tempts us 🙂

  4. I have seen this exact same thing. It’s almost like it doesn’t update the roles, it may take a minute to clear out, sometimes I’ve seen it update and go away, other times it did not.

  5. I Think you have issues of permisson… do you try it with a query with the permissions exactly? and did you look at the database if was the user right there? the account has the right permission to delegate permissions to other accounts.

Leave a Reply to Nikodem Cancel reply

Your email address will not be published. Required fields are marked *