You can create replication definitions using extended limits for both replicate and standby databases. Extended limits are defined as:
Wide columns – data rows containing more than 255 to a maximum of 32768 bytes.
More columns – replication definitions containing more than 250 columns in a replication definition.
Wide data – data rows up to the size of the data page on the data server. Adaptive Server version 12.5 and later supports page sizes of 2K, 4K, 8K, and 16K.
Wide messages – messages larger than 16K.
Replication Server can replicate wide columns containing char, varchar, binary, univarchar, unichar, unitext or Java inrow data to a maximum of 32768 bytes. Maximum column width on each system may vary; it is a function of the total number of columns and the page size of the data server.
You can use wide columns as primary keys and searchable columns and in replication definition where clauses.
The maximum number of bytes in the where clause
of a subscription or article is 255 bytes. You cannot use wide columns
in the where clause of subscriptions or articles.
There is no explicit limit on the number of columns in a replication definition. Replication Server does not limit the number of primary key or searchable columns.
Replication Server uses primary key columns to build where clauses of SQL statements for the data server. Consider data server limitations when determining the actual number of columns available for primary keys in replication definitions.
Similarly, although Replication Server imposes no limits on the number of searchable columns in a replication definition, the number of columns in the where clause of a subscription or article may also be constrained by data server limitations.
Data rows can equal the size of the data page on the data server. Adaptive Server version 12.5 and later supports page sizes of 2K, 4K, 8K, and 16K.
Replication Server copies data rows as messages in stable queues manage by the SQM. These messages contain before and after images of replicated data rows as well as other information. They require significantly more space than the data rows on which they are based. With extended limits, messages can span blocks and are no longer limited to 16K.
