Avatar of MicroAutomation
MicroAutomation
 asked on

SQL Transactional replication trouble

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

Avatar of undefined
Last Comment
MicroAutomation

8/22/2022 - Mon
MicroAutomation

ASKER
Thanks. Not sure how I chose the wrong zone but definitely needed to be moved.
venk_r

Is there any custome stored procedures involved in this replication.
?Is the distribution Server on a separate server and is that being shared by both the subscriptions?
MicroAutomation

ASKER
No there is no custom stored procedure in use for this.

The Distribution server is a separate server it is being shared by both subscriptions. It is setup to allow each both Publishers to use it. Both publishers are using separate distrib databases. At least as far as I can tell they are.
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
William Peck
venk_r

If its more than one distribution database please verify the setup by going thru the below link and make sure they'r setup correctly.The distributor may have been pointing to same destination.

http://www.sqlservercentral.com/articles/Replication/69663/
MicroAutomation

ASKER
At the distributor we have separated the distribution databases, locations, snapshot folders, etc for each publication. We have read the link and reviewed all the distributor settings.

Same results.
MicroAutomation

ASKER
Any other thoughts on this?
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
ASKER CERTIFIED SOLUTION
MicroAutomation

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
MicroAutomation

ASKER
We have corrected the problem on our own. Thanks.