ConnectStrForMaster

Connection string that the master server must use to communicate with the replica server.

This information is read when the replica server is started. The connect string is sent to the master as part of each message from the replica to the master.

For example:

none

RW

Replica

MasterStatementCache

Maximum number of statements used during one propagation in the master database.

The statement cache is used to store prepared statements received by the master database in one propagation from the replica database.

10

RO

Master

RefreshIsolationLevel

Transaction isolation level to use for refresh operations, instead of using the solid.ini default value.

The following values are valid:

Same as SQL.IsolationLevel

RW

Master

RefreshReadLevelRows

Number of rows after which the read level is released in the master server, if the used isolation level is READ COMMITTED.

With other isolation levels, the read level is kept for the full time of the refresh operation. The read level denotes a snapshot-consistent version of the data in the whole database. By releasing the read level, you avoid keeping too much data in main memory during the refresh operation.

See also, Srv.RemoteStartTasks

1000

RW

Master

ReplicaRefreshLoad

Amount of system processing capacity (as a percentage of full capacity) that is used to perform a refresh in the replica.

If you want to reserve some capacity for local processing in parallel with refresh, set this parameter to a value less than 100.

Possible values range from 0 to 100.

Values of 0 or 100 mean that full processor capacity is used.

If this parameter is set to 0 or to 100, you can set the system processing capacity with the bulletin board parameter SYS_SYNC_REPLICA_REFRESH_LOAD, see Parameters on replica.

100

RW

Replica

RpcEventThresholdByteCount

Minimum number of bytes that must be transmitted before the first and each subsequent SYNC_MSGBYTES_SENT or SYNC_MSGBYTES_RECEIVED event.

Events are not necessarily posted after exactly as many bytes as are specified in the parameter value. The server only checks the byte count after it has completed the sending of each communication packet (not each byte).

For example, if RpcEventThresholdByteCount is set to 1000, the message is 3500 bytes, and the packet size is 600 bytes, events are posted after the second packet (1200 bytes), the fourth packet (2400 bytes) and the fifth packet (3000 bytes).

0 (no events are posted)

RO

Master and replica