June 15, 2008 at 10:27 pm
HI to all .
Is there any procedure to copy the logins.
In logshipping logins are not transferred .
Is there any standard approach to copy the logins and move it to the secondary server.
Thanks,
Sandhya.
June 15, 2008 at 10:38 pm
Create an Integration Services package and schedule it to run daily/weekly, depending how often you add/remove logins. There is a "Transfer Logins Task" where you can select the logins that would have to be transferred along with some conditions; it's important to set "copySids" to True.
Good luck
June 15, 2008 at 11:52 pm
Here is a procedure to script the logins, but for log shipping you can make use of transfer login tasks as mentioned abovehttp://support.microsoft.com/kb/246133
[font="Verdana"]- Deepak[/font]
June 16, 2008 at 8:19 am
We tend to use the method specified in the Microsoft KB article. We also script out the logins and store it in a location that gets backed up to tape (which is then stored off-site) for disaster recovery situations.
K. Brian Kelley
@kbriankelley
June 16, 2008 at 2:16 pm
Deepak's link will give you what you want. Its been improved since I last needed it. Default databases etc. The key thing is the copying of the SIDs.
June 16, 2008 at 2:30 pm
Preet (6/16/2008)
Deepak's link will give you what you want. Its been improved since I last needed it. Default databases etc. The key thing is the copying of the SIDs.
This is a good point. The Microsoft scripts do ensure the SID is carried over. This is important because that's how the login maps into the database as a user. Without using the Microsoft scripts, you'd have to run sp_change_users_login to reconcile whenever you had to switch-over to the standby system.
K. Brian Kelley
@kbriankelley
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply