User's Manual

The better solution is to have a document_in_progress table. When the user
is done revising a document, the application moves it from the
document_in_progress table to the replicated table. The results in a single
update (200 kb of messages).
Controlling replication of
blobs
The Adaptive Server Anywhere BLOB_THRESHOLD option allows further
control over the replication of long values. Any value longer than the
BLOB_THRESHOLD option is replicated as a blob. That is, it is broken
into pieces and replicated in chunks, before being reconstituted by using a
SQL variable and concatenating the pieces at the recipient site.
By setting BLOB_THRESHOLD to a high value in remote Adaptive Server
Anywhere databases, blobs are not broken into pieces, and operations can be
applied to Adaptive Server Enterprise by the Message Agent. Each SQL
statement must fit within a message, so this only allows replication of small
blobs.
Replication of dates and times
When date or time columns are replicated, the Message Agent uses the
setting of the SR_Date_Format, SR_Time_Format, and
SR_Timestamp_Format database options to format the date.
For example, the following option setting instructs the Message Agent to
send a date of May 2, 1987 as 1987-05-02.
SET OPTION SR_Date_Format = ’yyyy-mm-dd’
☞ For more information, see “SQL Remote options” on page 315.
The following points may be useful when replicating dates and times:
♦ The time, date, and timestamp formats must be consistent throughout the
installation.
♦ If the consolidated database is an Adaptive Server Anywhere database,
ensure that the order of year, month, and day used for the date and
timestamp formats matches the setting of the DATE_ORDER database
option.
You can change the DATE_ORDER option for the duration of each
connection.
♦ If the consolidated database is an Adaptive Server Enterprise database,
ensure that the order of year, month, and day in the SQL Remote settings
is consistent with the dateformat setting in the Adaptive Server Enterprise
database.
84