<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 - General
»
Replication error: "field size too large"
Replication error: "field size too large"
Rate Topic
Display Mode
Topic Options
Author
Message
Roust_m
Roust_m
Posted Tuesday, February 01, 2011 9:25 PM
SSC Eights!
Group: General Forum Members
Last Login: Sunday, May 05, 2013 7:55 PM
Points: 961,
Visits: 1,530
Hi,
I've got two databases on the same server and replicate some tables from one database to another.
The replication is configured so not to drop the table if it exists, but to delete the data based on the filter if one exists. There are two tables on the subscriber that have some extra columns.
I get "field size too large" error when trying to replicate them.
Is there a workaround without having to make the publisher and the subscriber tables identical by schema?
Thanks.
Post #1057181
PaulB-TheOneAndOnly
PaulB-TheOneAndOnly
Posted Tuesday, February 01, 2011 9:30 PM
SSCrazy
Group: General Forum Members
Last Login: Today @ 1:08 PM
Points: 2,982,
Visits: 4,396
Roust_m (2/1/2011)
I've got two databases on the same server and replicate some tables from one database to another.
The replication is configured so not to drop the table if it exists, but to delete the data based on the filter if one exists. There are two tables on the subscriber that have some extra columns.
I get "field size too large" error when trying to replicate them.
Is there a workaround without having to make the publisher and the subscriber tables identical by schema?
Check column datatypes and sizes - size of a column in a suscriber table may be too short.
_____________________________________
Pablo (Paul) Berzukov
Author of
Understanding Database Administration
available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Post #1057183
Roust_m
Roust_m
Posted Tuesday, February 01, 2011 10:01 PM
SSC Eights!
Group: General Forum Members
Last Login: Sunday, May 05, 2013 7:55 PM
Points: 961,
Visits: 1,530
No, all the columns are identical, the only difference is that the subscriber has few extra columns.
Post #1057185
marcelo miorelli
marcelo miorelli
Posted Wednesday, October 10, 2012 8:56 AM
Grasshopper
Group: General Forum Members
Last Login: Monday, April 15, 2013 6:28 AM
Points: 14,
Visits: 176
hi gents,
has this been sorted?
I have got the same error.
Message: Field size too large
thanks and regards
marcelo
merge replication
sql server 2005 64 bits
Message: The process could not bulk copy into table '"dbo"."MSmerge_contents"'.
2012-10-10 14:28:51.872 Percent Complete: 0
2012-10-10 14:28:51.872 Category:NULL
Source: Microsoft SQL Native Client
Number: 0
Message: Field size too large
2012-10-10 14:28:51.919 Percent Complete: 0
Post #1370988
Gail Wanabee
Gail Wanabee
Posted Friday, October 12, 2012 11:58 AM
SSC Veteran
Group: General Forum Members
Last Login: Monday, May 06, 2013 2:26 PM
Points: 254,
Visits: 1,029
I'm no expert on this subject but I'm wondering if SQL Server has simply delivered an inappropriate error message.
Regarding the 2 extra columns you mentioned on the subscriber side: Are they constrained as "NOT NULL" columns?
I am only guessing that this might be a source of the problem.
Post #1372308
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
