<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by Yichang Chen
»
Resolving User Security Identifier (SID)...
Resolving User Security Identifier (SID) Discrepancy in Read-Only Databases
Rate Topic
Display Mode
Topic Options
Author
Message
dbychen
dbychen
Posted Monday, December 28, 2009 12:20 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Wednesday, February 13, 2013 2:32 PM
Points: 135,
Visits: 459
Comments posted to this topic are about the item
Resolving User Security Identifier (SID) Discrepancy in Read-Only Databases
Post #839327
timothyawiseman
timothyawiseman
Posted Tuesday, December 29, 2009 10:47 AM
Right there with Babe
Group: General Forum Members
Last Login: Thursday, February 14, 2013 12:01 PM
Points: 743,
Visits: 900
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
Paul White
Paul White
Posted Wednesday, December 30, 2009 3:05 AM
SSChampion
Group: General Forum Members
Last Login: Today @ 1:49 AM
Points: 10,990,
Visits: 10,540
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
dbychen
dbychen
Posted Wednesday, December 30, 2009 8:09 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Wednesday, February 13, 2013 2:32 PM
Points: 135,
Visits: 459
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
dbychen
dbychen
Posted Wednesday, December 30, 2009 8:13 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Wednesday, February 13, 2013 2:32 PM
Points: 135,
Visits: 459
Correct! This is another reason.
Thanks,
Yichang
Post #840349
timothyawiseman
timothyawiseman
Posted Wednesday, December 30, 2009 10:55 AM
Right there with Babe
Group: General Forum Members
Last Login: Thursday, February 14, 2013 12:01 PM
Points: 743,
Visits: 900
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 »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
