merge replication problem;urgent

We have a publisher and 2 subsribers. The
subscribers are spanning 2 transactions/sec. We have
implemented merge replication and it was scheduled
to occur every 5 min. When we ran it for the first time with a
transaction rate of 75k/hr it ran for 4 days.After sometime we got
problems so we reduced the transaction rate to 12k/hr then,
the replications is going on without any problem for
sometime(may be some hours), but after that it
failes with the message, "the process could not
deliver inserts at the publisher". When
I searched for this error in google, it asked me to
increase the queytimeout value in agent profile. So
I increased it from 300 to 600, but in vain. Now the merge agent is
failing as soon as it is started.We have a dedicated network for this
replication. If
anybody could help me in this, that would be great.
windows: windows 2003 server, sql server: sql server 2000 standard
edition.
Failing as soon as started, might be syntax error w/ QueryTimeout switch.
Confirm you added to end of Run Agent step:
-QueryTimeout 0
0 = unlimited
ChrisB
MCDBA OCP
www.MyDatabaseAdmin.com
"sqldbapree" wrote:

> We have a publisher and 2 subsribers. The
> subscribers are spanning 2 transactions/sec. We have
> implemented merge replication and it was scheduled
> to occur every 5 min. When we ran it for the first time with a
> transaction rate of 75k/hr it ran for 4 days.After sometime we got
> problems so we reduced the transaction rate to 12k/hr then,
> the replications is going on without any problem for
> sometime(may be some hours), but after that it
> failes with the message, "the process could not
> deliver inserts at the publisher". When
> I searched for this error in google, it asked me to
> increase the queytimeout value in agent profile. So
> I increased it from 300 to 600, but in vain. Now the merge agent is
> failing as soon as it is started.We have a dedicated network for this
> replication. If
> anybody could help me in this, that would be great.
> windows: windows 2003 server, sql server: sql server 2000 standard
> edition.
>
sql

merge replication problem ; very urgent

We have a publisher and 2 subsribers. The subscribers are spanning 2 transactions/sec. We have inplemented merge replication and it was scheduled to occur every 5 min. When we start the replication, the replications is going on without any problem for sometime(may be some hours), but after that it failes with the message, "the process could not deliver inserts at the publisher". We have SAN. When I searched for this error in google, it asked me to increase the queytimeout value in agent profile. So I increased it from 300 to 600, but in vain. If anybosy could help me in this, that would be great.

Thanks,

Preethi.

Hi Preethi,

Is this SQL 2000 or SQL 2005?
Is there a large amount of data yet to be propagated across when this failure occurs?
Are any other processes running on the Publisher machine that are taking up the CPU or memory and hence the merge agent timing out?
Are there any constraints on the publisher that are making the inserts to fail?
Can you post the complete error message from the Merge agent.
Also a higher verbosity log will help. Run the merge agent with the parameter -OutputVerboseLevel 2 or 3.|||sql 2000.
we have 4 merge agents running thats it.
i took an error log with the high verbosity level.
In job history, the error is "remote procedure call failed and it didn't execute".
In the log that I took, the above error message i gave occured. Actually when we started replication fresh, it ran for 4 days for transaction rate 75K/hr. Now even with 12K/hr it is failing in 3 min.

Regarding error i will post it.|||Are you using any agent profile to run the merges?
When you changed the Timeout value, where did you change it?
Try increasing the timeout and logintimeout values. Set -QueryTImeout 1000 -LoginTimeout 1000 and see if it helps.

Another thing you could try is setting the -UploadGenerationsPerBatch and -DownloadGenerationsPerBatch to a low value say 25 and run the merge agent.

Merge replication missing transactions

I have 2 servers, one running SQL 2000 and one running SQL 7. On the 2000 box I have 2 databases which are replicating between each other fine using Transactional replication. (One way replication only)

I also wish to use replication to keep a database on the SQL 7 box up to date. (Again the dataflow is ALL one way between the 3 databases)

I have set up Merge replication between these two due to transactional replication not working correctly between the different versions of SQL Server. (I belive this is due to SQL 7 using a date stamp as the unique ID on the table columns and 2000 using a GUID.)

Now whenever I issue an insert/update/delete to the first database in the chain, transactional replication updates the 2nd ok, but merge replication then fails to update the database on the 3rd server.

If I issue an insert/update/delete to the 2nd database in the chain the change is replicated correctly.

Any ideas?...Upgrade SQL2k to SP3. Microsoft have updated this but didn't publicise it at all!

If anyone has any problems with this email me at my username @.hotmail.com.

Cheers,|||Upgrade SQL2k to SP3. Microsoft have updated this but didn't publicise it at all!

If anyone has any problems with this email me at my username @.hotmail.com.

Cheers,

Merge Replication and transactions

I have one table in Merge Replication with dynamic filtering and
exchangetype=2 (from publisher to subscriber only), with Merge Agent
scheduled daily (night)
In this table I insert tipically some rows between two agent's run and I
would like to replicate each row as single transaction (i.e. what's happen if
I must to replicate three rows to a subscriber in single agent run but after
replication of first row network link between publisher and subscriber goes
down?).
Can I obtain this with three insert with three transactions on publisher
table (one insert, one transaction)?
Thanks in advance
Alexago,
unlike transactional, merge replication doesn't really have a concept of
transactions. Generation numbers are used as a logical clock, but this is a
different mechanish (see BOL). If the network link goes down, you can just
restart the merge agent and it will continue where it left off. If you are
concerned about the article processing order, have a look at this article:
http://support.microsoft.com/default.aspx?scid=kb;[LN];307356
HTH,
Paul Ibison