RE: Subscriber cannot "see" Publisher - and it's going to stay that wa

Hi Nexdeveloper,
Thanks for using Microsoft Online Managed Newsgroup.

From your discritpion, I understand that:
You had a transactional replication, however you found that the distributer
could access both the publisher and the subscriber though they coud not
directly access each other. I guess you think that in transactional
replication the distributer should only see the subscriber so that the
communication line can keep single direction.
If I have misunderstood, please let me know.

Transactional replication is implemented by the SQL Server Snapshot Agent,
Log Reader Agent, and Distribution Agent. The SQL Server Snapshot Agent is
located in the publisher; while the Log Reader Agent and Distribution Agent
are located in the distributor.

The Log Reader Agent monitors the transaction log of each database
configured for transactional replication and copies the transactions marked
for replication from the transaction log into the distribution database,
which acts as a reliable store-and-forward queue. The Distribution Agent
copies the initial snapshot files from the snapshot folder and the
transactions held in the distribution database tables to Subscribers.

As you can see, the Log Reader Agent needs to access transaction logs in
the publisher; the Distribution Agent is responsible for copying the
snapshot files and transactions to subscribers. So the distributor should
see both the publisher and the subscriber. However, in this case, the
publisher does not make any try to access the subscriber, which is only a
task of the distributor.

For more information, you can refer to:
How Transactional Replication Works
http://msdn2.microsoft.com/en-us/library/ms151706.aspx

Hope this helpful.

Please feel free to let me know if you have any other questions or
concerns. Have a great day!

Charles Wang
Microsoft Online Community Support

======================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

.

Relevant Pages

  • Re: Skipping transactions in Msrepl_Commands
    ... So when the distribution agent starts or polls the ... out what should go to the subscriber. ... > which transaction to get next next. ...
    (microsoft.public.sqlserver.replication)
  • Re: replicated commands not executed on the subscriber side?
    ... Unlike the replication procedure when changes made at Subscriber, ... Distribution Agent. ... In our case, when running following the distributed transaction, the ...
    (microsoft.public.sqlserver.replication)
  • Re: Question about snapshot replication and monitoring of msrepl_transactions in the dist.db
    ... other objects on the subscriber, and the bcp the data there. ... > distribution db the publisher_database_id is going to be the same. ... > noticed that this transaction count is not correct. ... > database have everything to do with the snapshot replication and not the ...
    (microsoft.public.sqlserver.replication)
  • Re: Would snapshot clean current log reader?
    ... backup up the transaction log (you are running ... Stopping the log reader agent will let the transactions pool in the ... The distribution agent will not distribute anything until ...
    (microsoft.public.sqlserver.replication)
  • Re: Server SQLTEST1 is not prepared to run the offloaded agent
    ... By default the distributor will be on the server which you created it on, ... If you are using a pull subscription you will have to enable the subscriber ... Your publisher by default will use the distribution database it ...
    (microsoft.public.sqlserver.replication)
Loading