February 16, 2013 at 12:54 pm
Comments posted to this topic are about the item Alter User
February 16, 2013 at 12:58 pm
Nice straightforward question. I had to do some reading because I didn't know teh answer, but for me that makes it a good question.
But I wonder why this strange restriction that alter user can't provide a login for a user who doesn't already have one exists. Presumably MS has some reason for it, but BoL just tells us about the restriction and doesn't give any reason for it (tha's fairly standard for BoL, of course).
Tom
February 17, 2013 at 11:10 am
Nice question thanks.
February 17, 2013 at 9:30 pm
Nice question to start with on Monday Morning. Got to learn something, I was not aware of. Thanks:-)
~ Lokesh Vij
Link to my Blog Post --> www.SQLPathy.com[/url]
Follow me @Twitter
February 17, 2013 at 11:48 pm
Nice question with having good basic information.
Thanks
Vinay Kumar
-----------------------------------------------------------------
Keep Learning - Keep Growing !!!
February 18, 2013 at 1:20 am
Interesting question, thanks.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
February 18, 2013 at 1:39 am
Koen Verbeeck (2/18/2013)
Interesting question, thanks.
+1
~ demonfox
___________________________________________________________________
Wondering what I would do next , when I am done with this one :ermm:
February 18, 2013 at 2:01 am
Nice one, thanks
February 18, 2013 at 3:28 am
Interesting question, thank you for posting.
Did not tried this before, so had really no idea , but bit search on offline BOL, was able to guess that opt-3 may be the answer.
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
February 18, 2013 at 5:08 am
Raghavendra Mudugal (2/18/2013)
Did not tried this before, so had really no idea , but bit search on offline BOL, was able to guess that opt-3 may be the answer.
+1
--
Dineshbabu
Desire to learn new things..
February 18, 2013 at 5:10 am
If somebody explains step by step on actually what happening will be very helpful..
--
Dineshbabu
Desire to learn new things..
February 18, 2013 at 7:52 am
Wow, interesting... and very odd.
I'd be curious to know the reason behind this restriction.
February 18, 2013 at 10:18 am
Really good one -- thanks!
February 18, 2013 at 11:37 am
Got this one right after a lot of reading.. Thanks for a good qotd..
___________________________________________________________________
If I can answer a question then anyone can answer it..trying to reverse the logic.. :hehe:
February 18, 2013 at 11:43 am
+1, I'm rather curious about that restriction and didn't find anything enlightening in BOL, which states:
The WITH LOGIN clause enables the remapping of a user to a different login. Users without a login, users mapped to a certificate, or users mapped to an asymmetric key cannot be re-mapped with this clause. Only SQL users and Windows users (or groups) can be remapped. The WITH LOGIN clause cannot be used to change the type of user, such as changing a Windows account to a SQL Server login.
The name of the user will be automatically renamed to the login name if the following conditions are true.
Does that mean that, should we end up with a user that is not mapped to any logins, the only recourse is to drop that user and recreate it as mapped?
Andre Ranieri
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply