Hello, We have the following replication scenario: 2 master servers that are involved in P2P communications. We'll call these Server A and Server B. Both of these servers have a P2P publication and subscription to each other. All of this is working fine. Server A and Server B each have another transactional replication publication. Two other servers (Server C and Server D) are subscribers to the transactional publication on Server A. These servers act as read only servers. Replication to Server C and Server D fail with an error indicating that the "sp_MSins_dbo..." procedures are being called with too many parameters. When I run a trace I see that Server A is trying to call this sproc on Server C and Server D with the @MSp2pPostVersion parameter which doesn't exist. The parameter @MSp2pPostVersion is used for peer to peer replication, but Server C and D aren't involved in that so I don't get why they would be called with that parameter. If we manually edit the replications procs on Server C and D and add this parameter then it works perfectly but this seems like a huge hack. Is there any way for Peer to Peer replication to co-exist peacefully with regular transactional replication? Hopefully this makes sense to everyone. Thanks for any feedback!
Though I'm not an expert in P2P replication side, but here are few thoughts:It is good to execute the data definition language (DDL) statements to modify theschema of published tables. For more information about supported schemachanges, see Making Schema Changes on Publication Databases. Also few links (you might have gone thru already), it helps to refere http://msdn.microsoft.com/en-us/library/ms152536.aspx & http://msdn.microsoft.com/en-us/library/ms147385.aspx