Logshipping issue

We are using SQL2005 Logshipping between our primary and secondary SQL
server. It works great but we do have one problem.
The systemdatabases can't be configured for logshipping by design. If I
create a new user or change something on an exsisting user this is not been
updated on my secondary server, because this is saved in the master database.
I can't just create the same user on the secondary server because all
userdatabase is readonly so I can't grant a user access on userdatabases.
How do you handle this issue? Do I have to reconfigure Logshipping everytime
I make changed in my master database?There is no problem if you just add a new user in a user database for an
existing login. But you have to manage any change you may make to the master
database. This includes adding a new login or any change to a login SID that
may screw up the mapping between the login and its users.
Take a look at these two KB articles and the discussions of sp_resolve_logins:
http://support.microsoft.com/kb/321247/en-us
http://support.microsoft.com/kb/314515/en-us
Linchi
"Thomas" wrote:
> We are using SQL2005 Logshipping between our primary and secondary SQL
> server. It works great but we do have one problem.
> The systemdatabases can't be configured for logshipping by design. If I
> create a new user or change something on an exsisting user this is not been
> updated on my secondary server, because this is saved in the master database.
> I can't just create the same user on the secondary server because all
> userdatabase is readonly so I can't grant a user access on userdatabases.
> How do you handle this issue? Do I have to reconfigure Logshipping everytime
> I make changed in my master database?