I'm Canadian myself:)
No, it won't. You would have to recreate the publication,
and then send the snapshot over to the subscriber again.
Query BOL for the entry "Strategies for Backing Up and
Restoring Transactional Replication", and you'll learn how
to restore a replication topology to the same server, but
it can't be done cleanly when restoring to another server.
Merge replication does have alternate sync partners, so if
one publisher goes off line, your subscriber can sync with
another.
Transactional replication does not support this though.
A clustering solution might work best for you in this case.
[quoted text, click to view] >-----Original Message-----
>If I restore a publication database performing
>transactional replication onto another server, will the
>subscriber recognize the publication? How do I plan for
>this type of move?
>
>Anjelina
>.
Eh no way! What city?
Thanks for the reply! I have read the "Strategies for
Backing Up and Restoring Transactional Replication"
Too bad it won't recognize the publication..
What do you mean by a clustering solution. How I
implement this?
Thanks,
Anjelina
[quoted text, click to view] >-----Original Message-----
>I'm Canadian myself:)
>
>No, it won't. You would have to recreate the
publication,
>and then send the snapshot over to the subscriber again.
>
>Query BOL for the entry "Strategies for Backing Up and
>Restoring Transactional Replication", and you'll learn
how
>to restore a replication topology to the same server,
but
>it can't be done cleanly when restoring to another
server.
>
>Merge replication does have alternate sync partners, so
if
>one publisher goes off line, your subscriber can sync
with
>another.
>
>Transactional replication does not support this though.
>
>A clustering solution might work best for you in this
case.
>
>>-----Original Message-----
>>If I restore a publication database performing
>>transactional replication onto another server, will the
>>subscriber recognize the publication? How do I plan for
>>this type of move?
>>
>>Anjelina
>>.
>>
>.
Don't see what you're looking for? Try a search.