Replicating mirrored dbs

Hello,
We're looking to replicate Database A to Database B. (transactional DB to a
reporting server).
Both database A and database B are mirrored. Can we setup replication from
database A to database B and have failover not interupt replication? I've
been playing around with a test setup and replication works fine until I
failover database A or database B. I've performed the steps outlined here as
best as I understand them:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/82796217-02e2-4bc5-9ab5-218bae11a2d6.htm
However once I failover either database, replication complains that it can't
connect to the publishing db or subscription db. (which makes sense since
they've failed over). Any direction or resources on setting this up would be
greatly appreciated.
Thanks in advance.
I forgot to mention this is one way transactional replication with no
updating subscribers.
"sqlboy2000" wrote:

> Hello,
> We're looking to replicate Database A to Database B. (transactional DB to a
> reporting server).
> Both database A and database B are mirrored. Can we setup replication from
> database A to database B and have failover not interupt replication? I've
> been playing around with a test setup and replication works fine until I
> failover database A or database B. I've performed the steps outlined here as
> best as I understand them:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/82796217-02e2-4bc5-9ab5-218bae11a2d6.htm
> However once I failover either database, replication complains that it can't
> connect to the publishing db or subscription db. (which makes sense since
> they've failed over). Any direction or resources on setting this up would be
> greatly appreciated.
> Thanks in advance.
|||No, but if you have a remote distributor you can use the alternate log
reader switch to have the standby come up and replicate to the remote
distributor and its subscribers. Have a look at the PublisherFailoverPartner
setting.
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
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:4BA4B447-CCB4-4402-B7DD-DAC7B03F31E2@.microsoft.com...
> Hello,
> We're looking to replicate Database A to Database B. (transactional DB to
> a
> reporting server).
> Both database A and database B are mirrored. Can we setup replication from
> database A to database B and have failover not interupt replication? I've
> been playing around with a test setup and replication works fine until I
> failover database A or database B. I've performed the steps outlined here
> as
> best as I understand them:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rpldata9/html/82796217-02e2-4bc5-9ab5-218bae11a2d6.htm
> However once I failover either database, replication complains that it
> can't
> connect to the publishing db or subscription db. (which makes sense since
> they've failed over). Any direction or resources on setting this up would
> be
> greatly appreciated.
> Thanks in advance.
|||Thanks. That parameter setting did the trick for the publisher failover, it's
pretty seamless. (We're using a remote distributor).
As to the subscriber failing over, I've created a script that drops the push
subscription to the former primary and recreates it for the failed over
subscriber. Not totally automatic, but I'll take it.
Thanks.
"Hilary Cotter" wrote:

> No, but if you have a remote distributor you can use the alternate log
> reader switch to have the standby come up and replicate to the remote
> distributor and its subscribers. Have a look at the PublisherFailoverPartner
> setting.
> --
> 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
>
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:4BA4B447-CCB4-4402-B7DD-DAC7B03F31E2@.microsoft.com...
>
>