Read-only database and orphaned users.

• Jerry Tienter-162701

  Say Hey Kid

  Points: 694

  More actions

  October 6, 2008 at 9:47 am

  #194088

  I have a read-only database used in log shipping and I have orphaned users that need to be fixed. Of course I get the message below but is there a way to fix orphaned users

  in a read-only db and what does the last part of the error message mean?

  Thanks.

  Server: Msg 3906, Level 16, State 1, Procedure sp_change_users_login, Line 196

  Could not run BEGIN TRANSACTION in database 'db_name' because the database is read-only.

  The row for user 'xxxxxxxxx' will be fixed by updating its login link to a login already in existence.

  xxxxxx = user account.

• Steve Jones - SSC Editor

  SSC Guru

  Points: 738013

  More actions

  October 6, 2008 at 11:26 am

  #881252

  You need to remove read only status, fix the users, then set it again.

  sp_change_users_login

• Jerry Tienter-162701

  Say Hey Kid

  Points: 694

  More actions

  October 7, 2008 at 8:36 am

  #881716

  Thanks. Management in the pursuit of faster and better web performance wants all reporting done against the log shipped database. This creates issues when it comes time to do a log restore and you need exclusive access to the database. I am thinking of switching from log shipping to incremental restores then I can update the copy of production without any problems.