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...
Showing posts with label articles. Show all posts
Showing posts with label articles. Show all posts
Monday, March 26, 2012
Friday, March 9, 2012
Publishing problem ...
Hello,
I have a problem when trying to publish articles for merge
replication. During execution of the snapshot agent I
receive the following error "The process could not bulk
copy out of table '[dbo].[table_name]'. Can anyone help
me with this problem?
Any help at all would be greatly appreciated!
Thanks in advance
Jim S.
Basically it means the snapshot agent locked up, timed out, was blocked, or
somehow deadlocked. What you do is stop and restart the snapshot agent. If
you are dealing with a large table, you may need to manually transfer it to
the subscriber. There are cases where the size of the table becomes nearly
impossible to get a snapshot to complete.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||Do I:
1. Just let the snapshot agent run until it fails
during the bcp process
2. Transfer all tables to the subscriber via dts
3. Create subscription using the 'do not create schema
and data option'
>--Original Message--
>Basically it means the snapshot agent locked up, timed
out, was blocked, or
>somehow deadlocked. What you do is stop and restart the
snapshot agent. If
>you are dealing with a large table, you may need to
manually transfer it to
>the subscriber. There are cases where the size of the
table becomes nearly
>impossible to get a snapshot to complete.
>--
>Mike
>Principal Mentor
>Solid Quality Learning
>"More than just Training"
>SQL Server MVP
>http://www.solidqualitylearning.com
>http://www.mssqlserver.com
>
>.
>
|||If it continues to fail, what I normally do is to separate out the table
that are failing into a separate publication. The ones separated out I use
the "do not create..." option and use DTS to manually transfer everything
over. It's ugly and full of trial and error, but it works. There aren't
any other good options at this point, because a snapshot has to complete in
order for transactions to start flowing. The interesting thing you will
find is that DTS will generally transfer the data in about 1/10 the amount
of time that the snapshot takes.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
I have a problem when trying to publish articles for merge
replication. During execution of the snapshot agent I
receive the following error "The process could not bulk
copy out of table '[dbo].[table_name]'. Can anyone help
me with this problem?
Any help at all would be greatly appreciated!
Thanks in advance
Jim S.
Basically it means the snapshot agent locked up, timed out, was blocked, or
somehow deadlocked. What you do is stop and restart the snapshot agent. If
you are dealing with a large table, you may need to manually transfer it to
the subscriber. There are cases where the size of the table becomes nearly
impossible to get a snapshot to complete.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||Do I:
1. Just let the snapshot agent run until it fails
during the bcp process
2. Transfer all tables to the subscriber via dts
3. Create subscription using the 'do not create schema
and data option'
>--Original Message--
>Basically it means the snapshot agent locked up, timed
out, was blocked, or
>somehow deadlocked. What you do is stop and restart the
snapshot agent. If
>you are dealing with a large table, you may need to
manually transfer it to
>the subscriber. There are cases where the size of the
table becomes nearly
>impossible to get a snapshot to complete.
>--
>Mike
>Principal Mentor
>Solid Quality Learning
>"More than just Training"
>SQL Server MVP
>http://www.solidqualitylearning.com
>http://www.mssqlserver.com
>
>.
>
|||If it continues to fail, what I normally do is to separate out the table
that are failing into a separate publication. The ones separated out I use
the "do not create..." option and use DTS to manually transfer everything
over. It's ugly and full of trial and error, but it works. There aren't
any other good options at this point, because a snapshot has to complete in
order for transactions to start flowing. The interesting thing you will
find is that DTS will generally transfer the data in about 1/10 the amount
of time that the snapshot takes.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
Subscribe to:
Posts (Atom)