<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Timothy Ford
»
Fixing Orphaned Users
11 posts, Page 1 of 2
1
2
»»
Fixing Orphaned Users
Rate Topic
Display Mode
Topic Options
Author
Message
Timothy Ford-473880
Timothy Ford-473880
Posted Monday, December 03, 2007 9:27 PM
Ten Centuries
Group: General Forum Members
Last Login: Tuesday, April 09, 2013 9:07 AM
Points: 1,004,
Visits: 424
Comments posted to this topic are about the item
Fixing Orphaned Users
- Tim Ford, SQL Server MVP
http://www.sqlcruise.com
http://www.thesqlagentman.com
http://www.linkedin.com/in/timothyford
Post #429094
happycat59
happycat59
Posted Monday, December 03, 2007 9:35 PM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 10:56 PM
Points: 2,468,
Visits: 2,061
I agree that this can be an issue but you can help yourself out a little by reviewing the syntax of the "CREATE LOGIN" or "sp_addlogin" commands.
Both of these commands allow you to specify the SID. If you are able to specify the same SID for the logins on each of the servers, you can happily backup/restore databases between instances and the login and user entries will match because you created the login on each instance with the same SID.
This is especially important when you are using log shipping or database mirroring. When a problem occurs and your primary server dies, there is one less issue that needs to be handled to get your standby database online. In the case of mirroring, ensuring that you use the same SID allows you to automatically bring the mirroring online with no intervention required.
Post #429095
Andy Warren
Andy Warren
Posted Tuesday, December 04, 2007 6:54 AM
SSCertifiable
Group: Moderators
Last Login: Thursday, May 09, 2013 12:38 PM
Points: 6,462,
Visits: 1,384
I agree that sync'ing SID's is a pretty good idea. MS also has a script up on MSDN that will script out all your logins along with the encrypted passwords so you can just run it against the other server and be done.
Andy
SQLShare - Learn One New Thing Each Day
SQLAndy - My Professional Blog
Connect with me on LinkedIn
Follow me on Twitter
Post #429260
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Tuesday, December 04, 2007 7:45 AM
SSC-Dedicated
Group: Administrators
Last Login: Yesterday @ 2:54 PM
Points: 31,410,
Visits: 13,726
sp_helprevlogin is the procedure, but it's a 2005 one only now. They updated it. The original for 7/2000 is available in the script library here.
http://www.sqlservercentral.com/scripts/Maintenance+and+Management/31711/
Nice article, Tim!
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #429308
Charles Kincaid
Charles Kincaid
Posted Tuesday, December 04, 2007 9:57 AM
Right there with Babe
Group: General Forum Members
Last Login: Friday, May 17, 2013 9:18 AM
Points: 772,
Visits: 1,825
Great article Tim. Thanks. You said:
You can add the login to the SQL instance and re-run the script thereby reconciling the user and login.
Since you are discussing moving from test to production would it not be better to scan for missing logins and removed those users by default? The thinking is more restriction is better so if the login does not exist on the server you can't
grant
permissions.
I have the same challenge in the opposite direction. I pull production databases and restore to our development servers. I had this problem in SQL 2000 but I found an odd work-around. If I stop and restart the service SQL seems to relink my logins by itself. :)
ATB
Charles Kincaid
Post #429421
Antares686
Antares686
Posted Tuesday, December 04, 2007 10:33 AM
SSCrazy Eights
Group: Moderators
Last Login: Tuesday, April 09, 2013 12:53 PM
Points: 8,357,
Visits: 684
This is what I personally use
select 'exec sp_change_users_login ''AUTO_FIX'',''' + [name] + '''', * from sysusers where status != 0 and uid > 2
it builds a string for each account, then I take and run the resultset in another window.
Post #429441
Thomas LeBlanc
Thomas LeBlanc
Posted Tuesday, December 04, 2007 3:43 PM
SSCrazy
Group: General Forum Members
Last Login: Yesterday @ 3:33 PM
Points: 2,700,
Visits: 717
What is the difference between Auto_Fix and Update_One?
ThomasLL
Thomas LeBlanc, MCITP DBA 2005, 2008 & MCDBA 2000
http://thesmilingdba.blogspot.com/
Post #429560
Antares686
Antares686
Posted Wednesday, December 05, 2007 7:35 AM
SSCrazy Eights
Group: Moderators
Last Login: Tuesday, April 09, 2013 12:53 PM
Points: 8,357,
Visits: 684
ThomasLL (12/4/2007)
What is the difference between Auto_Fix and Update_One?
ThomasLL
AUTO_FIX matches based on the user alias in the DB to a login account.
UPDATE_ONE allows you to specify the alias mapping to the login account.
See BOL for more detail if needs be.
Post #429773
Timothy Ford-473880
Timothy Ford-473880
Posted Wednesday, December 05, 2007 8:05 AM
Ten Centuries
Group: General Forum Members
Last Login: Tuesday, April 09, 2013 9:07 AM
Points: 1,004,
Visits: 424
I used to use sp_update_user_logins all the time, but with 80+ servers and almost 1,000 databases that I support without aid of a Jr. DBA I had to abandon that for something more automated and global across multiple logins at one time. It is a great stored proc though.
- Tim Ford, SQL Server MVP
http://www.sqlcruise.com
http://www.thesqlagentman.com
http://www.linkedin.com/in/timothyford
Post #429790
Dmitriy Burtsev
Dmitriy Burtsev
Posted Thursday, December 06, 2007 1:52 PM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, May 16, 2013 12:50 PM
Points: 45,
Visits: 225
I also have similar problem.
Step 1.
Create the file get_users_login.sql
select 'exec sp_change_users_login ' + quotename('Update_One', char(39)) + ',' + quotename(sl.name, char(39)) + ',' + quotename(su.name, char(39)) + ';'
from master.dbo.syslogins sl
join dbo.sysusers su on sl.sid = su.sid
where sl.hasaccess = 1
and sl.isntname = 0
and sl.name not in ('guest', 'dbo', 'sys', 'INFORMATION_SCHEMA')
Step 2.
osql get_users_login.sql -o fix_users_login.sql -w 2048 -n -h-1
Step 3.
Run osql fix_users_login.sql against any other server
Post #430424
« Prev Topic
|
Next Topic »
11 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
