Replication Problems

We are thinking to replicate a 'READ ONLY' database to an
off-site location by using a third party utility (We will
try to replicate from the warm backup server where we
restore transaction logs every hour from the original prod
server). Here are the two facts:
1- We don't want any performance decrease from the
original production server to replicate directly from the
prod server.
2- The third party utility is a file replication utility
which can replicate the whole database, differences only
e.t.c.
The problem seems to be, when the transaction log restore
starts, it kicks out all other users (SINGLE_USER,
RESTRICTED_USER).
Is there a way to restore the Transaction log without
cutting all the connections (Especially replication) to
the read-only database '
Thanks for any feedback....> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
I'm afraid not.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:b48d01c3ecfc$63946850$a101280a@.phx.gbl...
> We are thinking to replicate a 'READ ONLY' database to an
> off-site location by using a third party utility (We will
> try to replicate from the warm backup server where we
> restore transaction logs every hour from the original prod
> server). Here are the two facts:
> 1- We don't want any performance decrease from the
> original production server to replicate directly from the
> prod server.
> 2- The third party utility is a file replication utility
> which can replicate the whole database, differences only
> e.t.c.
> The problem seems to be, when the transaction log restore
> starts, it kicks out all other users (SINGLE_USER,
> RESTRICTED_USER).
> Is there a way to restore the Transaction log without
> cutting all the connections (Especially replication) to
> the read-only database '
> Thanks for any feedback....|||Change the schedule for the restore portion of transaction logshipping so that it doesn't conflict with the replication. Why are you using a third-party replication tool?