The database connection parameters dsi_serialization_method and dsi_partitioning_rule have changed.
dsi_serialization_method specifies how and when parallel DSI threads can start. It includes these new or changed options:
no_wait – specifies that a transaction can start as soon as it is ready—without regard to the state of other transactions.
wait_for_start – specifies that a transaction can start as soon as the transaction scheduled to commit immediately before it has started. Replaces the none option. When used with the origin partitioning parameter, this option replaces the single_transaction_per_origin serialization method.
isolation_level_3 – is the same as wait_for_start, except that DSIs will specify isolation level 3 when connecting to the replicate database.
wait_for_commit – specifies that a transaction can start only when the previous transaction is ready to commit.
none – maintained for backward compatibility. Replaced by wait_for_start.
single_transaction_per_origin – maintained for backward compatibility. Replaced by dsi_serialization_method set to wait_for_start and dsi_partitioning_rule set to origin.
dsi_partitioning_rule specifies the partitioning rules the DSI uses to partition transactions among available parallel DSI threads. It includes these new options:
origin – specifies that transactions with the same origin must be serialized when applied to the replicate database.
origin_sessid – specifies that transactions with the same origin and the same process ID (SPID in Adaptive Server) must be serialized when applied to the replicate database. The LTL version must be 600 or later.
Sybase recommends that you try setting dsi_partitioning_rule to origin_sessid, time as this setting may provide the most efficient partitioning.
