Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content
Qlik Resources

Calculating the Salesforce quota

The Salesforce endpoint leverages Salesforce APIs to provide Full Load and Change Processing replication functionality. When using the Salesforce endpoint, it's important to be aware of the API quota limits in order to plan your replication tasks accordingly.

Replicate utilizes the following Salesforce APIs:

  • SOAP API requests - Used for Full Load and Apply Changes replication tasks. This API will be used for Full Load when the Soap API option is selected in the Advanced tab.
  • Bulk API 2.0 - Used for Full Load and Apply Changes replication tasks. This API will be used for Full Load when the Bulk API option is selected in the Advanced tab (the default). In some cases, such as lookup and replication of metadata, the Soap API will be used even when Bulk API is selected.

SOAP API and Bulk API 2.0 consumption can be monitored using Salesforce REST API requests (see https://developer.salesforce.com/docs/atlas.en-us.238.0.api_rest.meta/api_rest/resources_limits.htm). The results of these requests are written to a JSON file containing current quota consumption values. The relevant value from a Replicate perspective is DailyApiRequests which is the current SOAP API quota and DailyBulkV2QueryJobs, which is the current Bulk API 2.0 quota.

For information about the Bulk API quota and its limits, and for information on monitoring Bulk API 2.0 consumption, refer to the Salesforce Developer Help.

Quota consumption by Replicate:

Replicate tasks consume approximately 20 SOAP API requests per table (for metadata and test connections). The actual number of requests consumed is proportionate to the number of tables being replicated: the greater the number of tables, the lesser the number of requests required per table.

Information noteThe estimations below are also true for a single CDC round. For an explanation of the term "round", see Setting general connection properties.

When Bulk API 2.0 is used

The endpoint consumes a single Bulk API 2.0 request per table and a single SOAP API request per data chunk.

For each table:

  • Bulk API 2.0:

    1 unit

  • SOAP API:

    5-20 units + [number of chunks (default chunk size is 100,000 rows)] units

Example:

A table with 1,000,000 rows will use a single Bulk API 2.0 unit and approximately 25 SOAP API units.

When SOAP API is used

For every 200 rows unloaded, one quota unit is consumed. For example, a table with 1000 rows will consume five quota units.

For each table:

5-20 Units + (rows of table /~200 rows) units

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here