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?

Logshipping Help Needed

I am setting up log shipping between a primary server and two secondaries.

The first (secondary ) is applying the logs fine but the second is generating the following error.

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3154: [Microsoft][ODBC SQL Server Driver][SQL Server]The backup set holds a backup of a database other than the existing 'CDE2' database.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally.

the logshipping monitor says it failes to apply first_file_0000000000...Trn

I have seen this listed on MS KB Base Article - 311801 .

and have followed all the suggestions to resolve this issue including seperate folders for each log ship but to no avail.

Any help would be greatly appreciated.

Thanks in advanceDIsable the LS and apply full backup on secondary server, then enable LS again.sql

Logins with Log shipping

We are planning on using our secondary database as a reporting server with
log shipping. The problem is that log shipping puts the db in read only mode
and occasionally we need to add user permissions to the secondary only. The
only option I see is everytime permissions are needed we would have to take
the database out of read only mode, grant the permissions and then put the db
back to read only. Does anyone have any other ideas that might work? Thanks!
this won't work - by making the change you will break the log shipping
chain.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Anita" <Anita@.discussions.microsoft.com> wrote in message
news:6C1A0C65-2281-45A8-9A9C-5762DA7D9E6D@.microsoft.com...
> We are planning on using our secondary database as a reporting server with
> log shipping. The problem is that log shipping puts the db in read only
mode
> and occasionally we need to add user permissions to the secondary only.
The
> only option I see is everytime permissions are needed we would have to
take
> the database out of read only mode, grant the permissions and then put the
db
> back to read only. Does anyone have any other ideas that might work?
Thanks!
|||Anita,
you could add a separate role to the primary server and assign all the
necessary permissions there. Also, add a login to this role. As long as you
have the same login on the secondary server (same SID) the permissions will
be applicable there.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)