What is the maximum SQL Remote message size?
The maximum message size is usually governed by the platform and transport mechanism chosen. For example 16-bit VIM limits messages to 20,000 bytes. The -l switch on DBRemote controls the maximum size that will actually be built. You must keep the -l size the same on all databases participating in the same replication system. In versions prior to 5.5, the -l switch also controlled the size of the largest operation that could be replicated. In these versions a operation had to fit into a single message. If you had an insert of a longvarchar or longvarbinary the message size had to be big enough to hold the entire INSERT statement. This made replication of BLOBs (Binary Large Objects) impossible on some message transports. In version 5.5 and beyond we added the ability to break BLOB values into smaller chunks using a series of SET variable = variable || ‘more stuff’. This has removed the restrictions on replicating BLOBS and the -l switch is now only needed to ensure that the message siz
