Solved

SQL Transactional replication trouble

Posted on 2012-12-27
9
261 Views
Last Modified: 2013-01-15
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...
0
Comment
Question by:MicroAutomation
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 2
9 Comments
 

Author Comment

by:MicroAutomation
ID: 38725459
Thanks. Not sure how I chose the wrong zone but definitely needed to be moved.
0
 
LVL 8

Expert Comment

by:venk_r
ID: 38725611
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?
0
 

Author Comment

by:MicroAutomation
ID: 38725638
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.
0
Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

 
LVL 8

Expert Comment

by:venk_r
ID: 38725676
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/
0
 

Author Comment

by:MicroAutomation
ID: 38728606
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.
0
 

Author Comment

by:MicroAutomation
ID: 38733424
Any other thoughts on this?
0
 

Accepted Solution

by:
MicroAutomation earned 0 total points
ID: 38753333
We have started again on this and have setup the initial distributor, publication and subscriber. The tables are being updated in near real-time at the subscriber successfully now. Now just need the other half.

Attached are the setups scripted out for each.

We need to add to this:

Distributor (single server for both publishers)
   - a second allowed publisher on the distributor called abas02 (or IVRNASC01P11)
   - needs to use its own abas02 db and abas02 folder

Publisher (second publishing server)
   - a second publisher with the same publication but everything is abas02 (or IVRNASC01P11)
   - the target tables also change from _as01 to _as02

Subscriber (single subscriber for both publications)
   - add second subscription same as the first but everything is abas02 (or IVRNASC01P11)
   - both publications come to same database on this server only target table names here are different. (_as01 & _as02)


Thanks for any continued assistance...
rep.zip
0
 

Author Closing Comment

by:MicroAutomation
ID: 38777548
We have corrected the problem on our own. Thanks.
0

Featured Post

Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to leverage one TLS certificate to encrypt Microsoft SQL traffic and Remote Desktop Services, versus creating multiple tickets for the same server.
Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
Using examples as well as descriptions, and references to Books Online, show the documentation available for date manipulation functions and by using a select few of these functions, show how date based data can be manipulated with these functions.

724 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question