Showing posts with label generate. Show all posts
Showing posts with label generate. Show all posts

Friday, March 30, 2012

Merge Replication-Apply BCP files

How can i apply a BCP files generate by Distributor in the Suscribers.

I don′t know wich parameters BCP.EXE need.

Thanks

Can you explain why you need to manually apply them? Is the merge agent not applying them for you?|||

I need to manually apply because there is few information, and i've configured suscription with the option to no send the schema tables.

I've configured the replication via internet (is slow for a very large tables)

But now i need to send data to the suscribers.

Thanks

|||

manually applying the bcp files is not recommended. If you're having problems, then let us know what they so we can walk you through a solution.

What part is slow, applying the snapshot to the subscribers? Are these large tables? Are you using filtering, and using the dynamic snapshots? Is the agent failing? How would bcp'ing the data across the internet be any faster than merge agent applying the snapshot?

|||

I only need to know how can apply manually the BCP files on the susbcribers.

Any body knows what parameters i have to use to do this.

Thanks

|||I thinks I am having same requirements like Jorge,

See What I am looking for is quit similar to Jorge's case,

I have 2 Database Servers, I have set Merge Replication (Pull) between them,

But Sometimes The Connectivity between both of them is not available for many days, still data needs to be transfered through CD.

I thinks this problem is relavant, if not pls ignor, and pls give some solution

Friday, March 23, 2012

merge replication script problem

Hi all:
i set up merge replication with row and column filter in sql 2000 and
it works fine, so i generate the script and try to run this script in
another computer, i alway got errors like "table name does not exist etc",
those tables definately exist in DB.
i worked it out after i delete all column fiters in script, does any
one know what's the problem?
Cheers
nick
could you post your table schema and your publication script?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Nick" <fsheng@.ebreathe.co.nz> wrote in message
news:euoHn5JCFHA.936@.TK2MSFTNGP12.phx.gbl...
> Hi all:
> i set up merge replication with row and column filter in sql 2000
and
> it works fine, so i generate the script and try to run this script in
> another computer, i alway got errors like "table name does not exist etc",
> those tables definately exist in DB.
> i worked it out after i delete all column fiters in script, does any
> one know what's the problem?
>
> Cheers
> nick
>

Monday, March 12, 2012

Merge Replication Issue SQL Server 2005

I have set up merge replication with 1 publisher and 1 subscriber. Distribution is handled by a 3rd server.

I can generate a snapshot at the publisher and apply it to my subscriber. But when I insert some data (approx 30,000 rows) , the Synchronization agent gives the following error when It runs:

The merge process is retrying a failed operation made to article 'xxx' - Reason: 'The Merge Agent was unable to synchronize the row due to one or more unanticipated errors in the batch of changes. When troubleshooting, increase the -OutputVerboseLevel setting, restart the agent, and check for and resolve any errors generated by the database engine. '.

I have increased the OutputVerboseLevel setting and specified a file path in the -OutputMessageFile but the File is not being populated. All the references on books online say to put the file path in the -Output parameter but when I do it says it can only hold an integer value. So I cant see the errors generated by the database engine.

Could anybody please assist with this issue?

Thanks

If you increase the verbose level you should see the messges in MSmerge_history.

Also Merge replication doesnt use the distribution agent or much of the distribution database so its not useful to have a separate distributor.

Martin