The process could not bulk copy into table "dbo"."MSmerge_contents". Field size too large.



I am getting the following error when trying a merge replication:
The process could not bulk copy into table "dbo"."MSmerge_contents".
Field size too large.

I assume that the "field size too large" is significant but I do not
know what it is referring to and it seems completely out of my
control.

All the snapshot files download fine, it applies the .sch and .cft
files, bulk copies data into the main database tables and then says
that "the merge process was unable to deliver the snapshot to the
subscriber" and follows on with the error message above.

Some details:
publisher/distributor: SQL Server 2005 (workgroup edition)
subscriber: SQL Server 2005 Express
merge replication with web synchronisation
parameterised row filters used with (potentially) overlapping
partitions

The whole thing was working fine but I have been working on producing
a deployment package so I detached the database on the subscriber and
used the mdf file as the basis for the deployment (I have a feeling
that is the root cause of my problems). As part of the deployment I
copy in this mdf file (not the log file), attach using CREATE DATABASE
with the FOR ATTACH_REBUILD_LOG option. I also have various scripts in
the deployment to configure everything.

I have tried re-inititialising at the publisher and recreating the
snapshot but still the same error.

Any help greatly appreciated on this and any better way of setting up
the initial database before first synchronisation.
.



Relevant Pages

  • Help with Transactional Replicatoin Setup
    ... After working on setting up replication for a while I have finally got ... I’ve got a development database with 3 tables using DRI and an identity ... our production server that has been in use for years now. ... the distributor/publication and the production server is the subscriber. ...
    (microsoft.public.sqlserver.replication)
  • Re: Sp_adjustpublisheridentityrange and resetting identity range
    ... > identity ranges you have set on your publisher. ... > ranges which will work for the lifetime of their replication solution. ... > should apply this value on the subscriber. ... >> restored the published database from a backup. ...
    (microsoft.public.sqlserver.replication)
  • Re: Sp_adjustpublisheridentityrange and resetting identity range
    ... The first problem could be related to one of two things. ... Do an sp_help mpwWebReturnMsg on your subscriber ... Looking for a SQL Server replication book? ... > restored the published database from a backup. ...
    (microsoft.public.sqlserver.replication)
  • Re: Blocking Issues
    ... locking with the replication process. ... triggers on the subscriber? ... Director of Text Mining and Database Strategy ... I have a publisher database which is replicating to ...
    (microsoft.public.sqlserver.replication)
  • Re: Blocking Issues
    ... see which queries come to the top. ... Your subscriber is the bottleneck here, I doubt replication is the problem ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)

Loading