We have used the same tables in both publications and we have some success.
If we make a change on a table on the SQL Server that is the publisher then
the change is replicated to the client but if we make a change on another SQL
server the change is replicated via peer to peer to all SQL Servers but the
change is not replicated via merge to the client
Any ideas.
[quoted text, click to view] "Hilary Cotter" wrote:
> Yes, it is. Ideally the same tables will not be published in the same
> publications however.
>
> --
> 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 > "Stephen" <Stephen@discussions.microsoft.com> wrote in message
> news:829912FF-8B7C-464D-A077-3BF3DC6487F5@microsoft.com...
> > We have 3 SQL 2005 Servers which are in a peer to peer replication
> > topology
> > but would also like to use merge replication to some remote clients.
> > Is it possible to have a database peing published in peer to peer and
> > merge
> > replication on the same server.
>
>
Yes, it is. Ideally the same tables will not be published in the same
publications however.
--
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 [quoted text, click to view] "Stephen" <Stephen@discussions.microsoft.com> wrote in message
news:829912FF-8B7C-464D-A077-3BF3DC6487F5@microsoft.com...
> We have 3 SQL 2005 Servers which are in a peer to peer replication
> topology
> but would also like to use merge replication to some remote clients.
> Is it possible to have a database peing published in peer to peer and
> merge
> replication on the same server.