SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Yichang Chen / Resolving User Security Identifier (SID) Discrepancy in Read-Only Databases / Latest PostsInstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 26 May 2013 03:31:23 GMT20RE: Resolving User Security Identifier (SID) Discrepancy in Read-Only Databaseshttp://www.sqlservercentral.com/Forums/Topic839327-2569-1.aspx[quote][b]Paul White (12/30/2009)[/b]]One scenario where this might be useful is if the read-only database is a target of log shipping.[/quote]That makes a lot of sense. Thank you.Wed, 30 Dec 2009 10:55:50 GMTtimothyawisemanRE: Resolving User Security Identifier (SID) Discrepancy in Read-Only Databaseshttp://www.sqlservercentral.com/Forums/Topic839327-2569-1.aspxCorrect! This is another reason.Thanks,YichangWed, 30 Dec 2009 08:13:12 GMTdbychenRE: Resolving User Security Identifier (SID) Discrepancy in Read-Only Databaseshttp://www.sqlservercentral.com/Forums/Topic839327-2569-1.aspxThanks for your comment.The approach discussed is to synchronize the login/userid of the report instance with the corresponding one in the read only database. The suggestion you made could work temporarily. The userid's SID will be changed back again upon performing a full database restore, because a userid's SID in a read only database is simply inhereted from its primary production database.RegardsYichangWed, 30 Dec 2009 08:09:01 GMTdbychenRE: Resolving User Security Identifier (SID) Discrepancy in Read-Only Databaseshttp://www.sqlservercentral.com/Forums/Topic839327-2569-1.aspx[quote][b]timothyawiseman (12/29/2009)[/b][hr]I am curious, why would you want to do this instead of (temporarily) taking the database off of read only status and updating the SIDS and then returning it to read only status?[/quote]One scenario where this might be useful is if the read-only database is a target of log shipping.Wed, 30 Dec 2009 03:05:29 GMTPaul WhiteRE: Resolving User Security Identifier (SID) Discrepancy in Read-Only Databaseshttp://www.sqlservercentral.com/Forums/Topic839327-2569-1.aspxA well written and good article that presents an interesting approach. I am curious, why would you want to do this instead of (temporarily) taking the database off of read only status and updating the SIDS and then returning it to read only status?Unless there is some reason to strictly keep it read only without exception, that seems a generally simpler answer with fewer potential side effects than this approach.Tue, 29 Dec 2009 10:47:39 GMTtimothyawisemanResolving User Security Identifier (SID) Discrepancy in Read-Only Databaseshttp://www.sqlservercentral.com/Forums/Topic839327-2569-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/Security/69001/">Resolving User Security Identifier (SID) Discrepancy in Read-Only Databases</A>[/B]Mon, 28 Dec 2009 00:20:57 GMTdbychen