We have setup a publication of TABLE_INFO on SERVER1 to TABLE_INFO_SERVER1 on a remote subscriber server. This works fine as all entries made at SERVER1 are being replicated to the remote subscriber server destination table of TABLE_INFO_SERVER1 successfully.
When we try adding a second subscription from another server of TABLE_INFO on SERVER2 to TABLE_INFO_SERVER2 the replication initializes correctly, but the SERVER1 table stops updating after initialization. Then instead of SERVER1 going to its destination table and SERVER2 going to its destination table, all records from both SERVER1 and SERVER2 are now being delivered to the SERVER2 destination tables.
I have checked to ensure that the destination tables at the publisher are configured correctly already. The only thing I can think of is that SQL doesn't like that the name of source tables on both servers are the same. Any assistance is appreciated...
Microsoft SQL Server 2008Microsoft SQL Server
8/22/2022 - Mon
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst