Alternate Synchronisation Partner

I am using merge replication and trying to configure an alternate
synchronisation partner (ASP). My topology is V-shape and replication is
working OK as long as I do not perform a sync of the subscriber with the ASP.
My subscription contains articles having identity columns managed by merge
replication, and this is casuing me some grief due to error 'Violation of
PRIMARY KEY constraint...Cannot insert duplicate key in object
'MSrepl_identity_range'.'. For ASP, it is not possible to have different
publications to that of the Primary publisher, hence disabling automatic
range management is not an option. Does anyone have an answer to this problem?
Also, does anyone know if it is possible to implement redundancy with merge
replication, similar to a peer-to-peer topology available with transactional
replication in SQL Server 2005?
Paul
MCDBA, MCSE
ASP do not provide redundancy to merge replication topologies. What they do
is allow a merge subscriber to connect with another publisher if the main
publisher goes offline for a brief time. It is unable to parcel out new
identity ranges.
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
"Paul Mu" <PaulMu@.discussions.microsoft.com> wrote in message
news:51DAB05E-232F-4FF0-A89D-2B7EF6859258@.microsoft.com...
> I am using merge replication and trying to configure an alternate
> synchronisation partner (ASP). My topology is V-shape and replication is
> working OK as long as I do not perform a sync of the subscriber with the
ASP.
> My subscription contains articles having identity columns managed by merge
> replication, and this is casuing me some grief due to error 'Violation of
> PRIMARY KEY constraint...Cannot insert duplicate key in object
> 'MSrepl_identity_range'.'. For ASP, it is not possible to have different
> publications to that of the Primary publisher, hence disabling automatic
> range management is not an option. Does anyone have an answer to this
problem?
> Also, does anyone know if it is possible to implement redundancy with
merge
> replication, similar to a peer-to-peer topology available with
transactional
> replication in SQL Server 2005?
> --
> Paul
> MCDBA, MCSE