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.


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.

| 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 clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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