Resolving User Security Identifier (SID) Discrepancy in Read-Only Databases

  • Comments posted to this topic are about the item Resolving User Security Identifier (SID) Discrepancy in Read-Only Databases

  • 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/

  • 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.

  • 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

  • Correct! This is another reason.

    Thanks,

    Yichang

  • 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/

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply