InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 11:27:56 GMT20http://www.sqlservercentral.com/Forums/Topic1402166-1292-1.aspxI hope this link will help you..http://sqlscripthub.blogspot.in/2012/11/sqlworld.htmlFri, 04 Jan 2013 01:40:31 GMTVikas Pathakhttp://www.sqlservercentral.com/Forums/Topic1402166-1292-1.aspxAlso remember that sp_change_users_login is a depreciated command, it has been replaced by ALTER LOGIN and will be removed from a future release on SQL.Thu, 03 Jan 2013 04:35:46 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1402166-1292-1.aspx[quote][b]Rama Chandra Gowtham. Peddada (1/2/2013)[/b][hr]Attaching and restoring databases from one server instance to another are common tasks executed by a DBA.If we move our database to another SQL Server instance through any process, the new server might or might not have the same logins and the SIDs of these logins would probably be different from the SIDs of these logins in the original server. What this means is that, the sysusers table in the moved database has SIDs that are not matched with the login info in the master database on this new server. Therefore we get orphaned usersOnce the Database is restored on the new instance. Run the below commands to troubleshoot and fix the issue.-Command to generate list of orphaned usersUSE <DBNAME>GOsp_change_users_login @Action='Report'GO--Command to map an orphaned userEXEC sp_change_users_login 'Auto_Fix', '<Username>'GOIf a login name does not exists, you would have to create it first before doing the mapping. A quick way to do this is to use the following command which will create the login and then map the login to the user--Command to map an orphaned user to a login that is not present but will be createdEXEC sp_change_users_login 'Auto_Fix', '<Username>', null,'<pwd>'GO[/quote] you need to give credit to the main poster/blogger OR even paste his/her link.These are forum etiquettes :-)Thu, 03 Jan 2013 04:21:05 GMTBhuvneshhttp://www.sqlservercentral.com/Forums/Topic1402166-1292-1.aspx[quote][b]brangaraja (1/2/2013)[/b][hr]hi can you please any one tell me what is exactly orphaned users and when will use this one and how to troubleshoot?[/quote]For details see this link [url]http://www.mssqltips.com/sqlservertip/1590/understanding-and-dealing-with-orphaned-users-in-a-sql-server-database/[/url]Thu, 03 Jan 2013 04:19:23 GMTBhuvneshhttp://www.sqlservercentral.com/Forums/Topic1402166-1292-1.aspxAttaching and restoring databases from one server instance to another are common tasks executed by a DBA.If we move our database to another SQL Server instance through any process, the new server might or might not have the same logins and the SIDs of these logins would probably be different from the SIDs of these logins in the original server. What this means is that, the sysusers table in the moved database has SIDs that are not matched with the login info in the master database on this new server. Therefore we get orphaned usersOnce the Database is restored on the new instance. Run the below commands to troubleshoot and fix the issue.-Command to generate list of orphaned usersUSE <DBNAME>GOsp_change_users_login @Action='Report'GO--Command to map an orphaned userEXEC sp_change_users_login 'Auto_Fix', '<Username>'GOIf a login name does not exists, you would have to create it first before doing the mapping. A quick way to do this is to use the following command which will create the login and then map the login to the user--Command to map an orphaned user to a login that is not present but will be createdEXEC sp_change_users_login 'Auto_Fix', '<Username>', null,'<pwd>'GOWed, 02 Jan 2013 22:04:48 GMTRama Chandra Gowtham. Peddadahttp://www.sqlservercentral.com/Forums/Topic1402166-1292-1.aspxhi can you please any one tell me what is exactly orphaned users and when will use this one and how to troubleshoot? Thanks in Advance.Regards,Raja.Wed, 02 Jan 2013 21:46:02 GMTbrangaraja