Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We recently hit this error shortly after enabling replication on a table.

Length of LOB data (%1) to be replicated exceeds configured maximum %2

I've found solutions to this problem already:

However there's no explanation of what this configuration was there for in the first place. If we turn off the LOB size limit what side effects does that have - are we opening ourselves up to more issues in the future?

Thanks in advance.

share|improve this question
up vote 1 down vote accepted

The max text repl size options exists to limit how much LOB data can be added to a replicated column. If you turn off the LOB size limit and a user inserts a large amount of LOB data, latency will increase and replication will come to a crawl. The max text repl size option can be used to prevent this.

share|improve this answer
Thanks Brandon - do you know of any stats around this (i.e. how replication time scales with the size of the lob), or know whether the impact will be limited to the current table vs hitting all tables on that publisher/distributor/subscriber? – JohnLBevan Oct 19 '12 at 23:32

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.