I read several articles to this topic, and I couldnt understand, why
a SQL-Server-Subscriber need to connect to the distributor.
- I have a Server A in my LAN, publishing a Database, distributor is
the same Server A.
- using Push-Merge-Replikation
- Server B in the internet, behind a firewall
In http://support.microsoft.com/kb/321822 you can read, that you the 2
servers must be able to ping eachother.
Is this definitely true? The Merge-Agent is running on Server A, and
Server A can connect to Server B. Why does the subscriber B need to
connect to Server A?
If you would use Pull-Replication, and der Merge-Agent was running on
Server B, yes, then I could unterstand this.
If this fact is really true, then it is much more difficult to realize
such a default-scenario like I would like to use.
Andreas Lauffer, Germany
You will need connectivity at some point in time. Your subscriber can be
offline for long periods of time, but at some point in time, it must sync
with the publisher.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Now available on Amazon.com
http://www.amazon.com/gp/product/off...?condition=all
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Andreas Lauffer" <al@.lauffers.de> wrote in message
news:u1ie01tic78r09tpmdjl3vuusmk9om6c78@.4ax.com...
> I read several articles to this topic, and I couldnt understand, why
> a SQL-Server-Subscriber need to connect to the distributor.
> - I have a Server A in my LAN, publishing a Database, distributor is
> the same Server A.
> - using Push-Merge-Replikation
> - Server B in the internet, behind a firewall
> In http://support.microsoft.com/kb/321822 you can read, that you the 2
> servers must be able to ping eachother.
> Is this definitely true? The Merge-Agent is running on Server A, and
> Server A can connect to Server B. Why does the subscriber B need to
> connect to Server A?
> If you would use Pull-Replication, and der Merge-Agent was running on
> Server B, yes, then I could unterstand this.
> If this fact is really true, then it is much more difficult to realize
> such a default-scenario like I would like to use.
>
> Andreas Lauffer, Germany
>
>
|||Sure you need a connection at one time. But the question is in which
direction you need to connect.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:<uuQaNsZDFHA.1936@.TK2MSFTNGP14.phx.gbl>...[vbcol=seagreen]
> You will need connectivity at some point in time. Your subscriber can be
> offline for long periods of time, but at some point in time, it must sync
> with the publisher.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Now available on Amazon.com
> http://www.amazon.com/gp/product/off...?condition=all
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Andreas Lauffer" <al@.lauffers.de> wrote in message
> news:u1ie01tic78r09tpmdjl3vuusmk9om6c78@.4ax.com...
Monday, March 26, 2012
Push-Replication with Internet-Connection
Labels:
articles,
connect,
couldnt,
database,
distributor,
internet-connection,
microsoft,
mysql,
oracle,
push-replication,
server,
sql,
sql-server-subscriber,
whya
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment