Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Resolving User Security Identifier (SID) Discrepancy in Read-Only Databases Expand / Collapse
Author
Message
Posted Monday, December 28, 2009 12:20 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, September 4, 2014 4:19 PM
Points: 137, Visits: 494
Comments posted to this topic are about the item Resolving User Security Identifier (SID) Discrepancy in Read-Only Databases


Post #839327
Posted Tuesday, December 29, 2009 10:47 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, April 4, 2014 4:40 PM
Points: 751, Visits: 917
A 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.


---
Timothy A Wiseman
SQL Blog: http://timothyawiseman.wordpress.com/
Post #839950
Posted Wednesday, December 30, 2009 3:05 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: 2 days ago @ 8:59 AM
Points: 11,194, Visits: 11,166
timothyawiseman (12/29/2009)
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?
One scenario where this might be useful is if the read-only database is a target of log shipping.




Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #840234
Posted Wednesday, December 30, 2009 8:09 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, September 4, 2014 4:19 PM
Points: 137, Visits: 494
Thanks 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.

Regards
Yichang



Post #840342
Posted Wednesday, December 30, 2009 8:13 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, September 4, 2014 4:19 PM
Points: 137, Visits: 494
Correct! This is another reason.

Thanks,
Yichang



Post #840349
Posted Wednesday, December 30, 2009 10:55 AM


Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, April 4, 2014 4:40 PM
Points: 751, Visits: 917
Paul White (12/30/2009)]One scenario where this might be useful is if the read-only database is a target of log shipping.


That makes a lot of sense. Thank you.


---
Timothy A Wiseman
SQL Blog: http://timothyawiseman.wordpress.com/
Post #840474
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse