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)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment