Show TOC

rs_fillcaptableLocate this document in the navigation structure

Records estimated transaction rates in the <rs_captable> table for an existing replication definition.

Syntax
rs_fillcaptable <RepDefName>, <InChRateI>, <InChRateD>, <InChRateU>,
<OutChRateI>, <OutChRateD>, <OutChRateU>, <InTranRate>, <OutTranRate>, <DelFlag>
Parameters
RepDefName

The name of the replication definition.

InChRateI

The number of inserts per second, including inserts that are not replicated. The default is 15 inserts per second.

InChRateD

The number of deletes per second, including deletes that are not replicated. The default is 15 deletes per second.

InChRateU

The number of updates per second, including updates that are not replicated. The default is 15 updates per second.

OutChRateI

The number of inserts per second, excluding inserts that are not replicated. The default is 15 inserts per second.

OutChRateD

The number of deletes per second, excluding deletes that are not replicated. The default is 15 deletes per second.

OutChRateU

The number of updates per second, excluding updates that are not replicated. The default is 15 updates per second.

InTranRate

The number of transactions per second for the database. The default is 5 transactions per second.

OutTranRate

The number of replicated transactions per second for the database. The default is 5 transactions per second.

DelFlag

Set to “n” or “N” to update the row for the replication definition. Set to “y” or “Y” to delete the row for the replication definition from <rs_captable>. Set <DelFlag> to “Y” and <RepDefName> to “ALL,” to clear the entire< rs_captable> table.

Examples
Example 1

In this example scenario, the overall transaction rate in a primary database is 10 transactions per second. Of these 10 transactions, 8 are replicated. The <InTranRate> for the database is 10 and the <OutTranRate> is 8.

There are two replicated transactions, T1 and T2. T1 executes 5 times per second, performs 2 updates to <table1>, and performs 1 update to <table2>. T2 executes 3 times per second, performs 2 inserts to <table1>, and performs 1 insert to <table2>.

There are two subscriptions in replicate databases, each receiving one half of the replicated data. The transactions are distributed equally across the two subscriptions. Therefore, the outbound estimates are 50 percent of the inbound estimates.

This table summarizes the information from this example scenario:

table1

table2

ins

upd

del

ins

upd

del

Inbound

T1 (5 per second)

10

5

T2 (3 per second)

6

3

Totals

6

10

8

Outbound

50% replicated

3

5

4

To get an estimate of stable queue size requirements for this example scenario, first clear the <rs_captable> table. Then use rs_fillcaptable with the parameters described above. When you are done, use the rs_capacity stored procedure with the new contents of the <rs_captable> table.

Example 2

This example clears the <rs_captable> table.

rs_fillcaptable @RepDefName = ’ALL’, @DelFlag = ’Y’
Example 3

This example fills the <rs_captable> table with the appropriate values for the first replication definition.

rs_fillcaptable
 repdef1, /* replication definition for table1 */
 6,      /* InChRateI */
 0,      /* InChRateD */
 10,     /* InChRateU */
 3,      /* OutChRateI */
 0,      /* OutChRateD */
 5,      /* OutChRateU */
 10,     /* InTranRate */
 8,      /* OutTranRate */
 n       /* DelFlag */
Example 4

This example fills the <rs_captable> table with the appropriate values for the second replication definition.

rs_fillcaptable
 repdef2, /* replication definition for table2 */
 8,      /* InChRateI */
 0,      /* InChRateD */
 0,      /* InChRateU */
 4,      /* OutChRateI */
 0,      /* OutChRateD */
 0,      /* OutChRateU */
 10,     /* InTranRate */
 8,      /* OutTranRate */
 n       /* DelFlag */

See rs_capacity for more information on using the output derived from these examples to complete the estimate of stable queue size requirements.

Usage
  • Use rs_fillcaptable to describe the transactions for each replication definition you want to include in your stable queue estimate.

  • rs_fillcaptable maintains a work table named <rs_captable> that contains estimates of change rates for each replication definition in a database.

  • Use the output of rs_fillcaptable as input for the rs_capacity stored procedure.