"Paul" <gupta@spireite.ndo.co.uk> wrote in message
news:1m0k9e58hav11.o8syq1rq50xp.dlg@40tude.net...
> Thanks for that - its what I feared really.
>
> I assume then, that if the databases failover, that the SQL2000 box won't
> know and will just keep retrying to the primary.
>
> If 2005 is publishing to a database mirrored pair of servers, is that
> intelligent enough to actually switch to the failover if the primary is
> down? I can probably get the an upgrade purchased.
>
> Thanks in advance
>
>
>
>
>
> On Thu, 13 Sep 2007 11:02:27 -0400, Hilary Cotter wrote:
>
>> Yes, it can be done. As long as you replicate to the primary.
>>
>> You will need to manage your topology using SSMS, or create an alias to
>> your
>> primary using client network utility on the publisher and use the procs
>> to
>> create your subscriber.
>>
>> Replication Monitor does provide more features and metrics than SQL 2000
>> Replication Monitor or Replication Monitor Group. To take advantage of
>> these
>> your publisher/distributor would need to be SQL 2005. If you can afford
>> it I
>> would use SQL 2005.