Transaction-Partitioning Rules

Replication Server allows you to partition transactions for each connection according to one or more attributes.

alter connection to data_server.database
	set dsi_partitioning_rule to ‘{ none|rule[, rule ] }’

alter connection to TOKYO_DS.pubs2
    set dsi_partitioning_rule to ‘user,time’

• Partitioning Rule: Origin
  origin causes transactions from the same origin to be serialized when applied to the replicate database.
• Partitioning Rule: Origin and Process ID
  origin_sessid causes transactions with the same origin and the same process ID to be serialized when applied to the replicate database.
• Partitioning Rule: None
  none is the default behavior, in which the DSI scheduler assigns each transaction group or large transaction to the next available parallel DSI thread.
• Partitioning Rule: User
  If you choose to partition transactions according to user name, transactions entered by the same primary database user ID are processed serially. Only transactions entered by different user IDs are processed in parallel.
• Partitioning Rule: Origin Time Begin and Commit Times
  If the time partitioning rule is used, the DSI scheduler looks at the origin begin and commit times of transactions to determine which transactions could not have been executed by the same process at the primary database.
• Partitioning Rule: Name
  The DSI scheduler can use transaction names to group transactions for serial processing.
• Partitioning Rule: Ignore Origin
  ignore_origin overrides the default handling of transactions from different origins, and allows them to be partitioned as if they all came from the same origin.