Understanding Records in Skyvia Data Integration

Understanding Records in Skyvia Data Integration

1.1 Understanding Records in Skyvia Data Integration

A record in Data Integration represents a single row in a database table. Every integration process—Import, Replication, Export, Synchronization, etc —handles individual records.

Records also serve as a measurement unit. You can track processed records in the run history, which shows how many were successfully processed versus how many encountered errors.

For more details, refer to the Data Integration documentation and the Integration Run History section.

1.2 How Skyvia Tracks Records

Skyvia pricing plans are based on the number of records processed per month. This includes:

  • Import & Replication: Records created, updated, or deleted in the target system. (Even if an update doesn’t change the data, it still counts.)
  • Export: Rows included in CSV files generated during export operations.
  • Synchronization: Records successfully created, updated, or deleted in both the source and target systems.
  • Data & Control Flows: All successfully processed rows in Target components, except those using cache or log connections.

For a complete breakdown, check the links below.

1.3 Checking Your Record Usage

You can monitor record consumption using the Usage Summary feature. This tool lets you:

  1. Track used vs. remaining resources
  2. View usage statistics for a specific period
  3. Group data by workspace or integration
  4. Break down record usage by time frame for better tracking

For more details, visit our Usage Summary documentation.

    • Related Articles

    • Data Integration: You have reached the limit of records

      The error "You have reached the limit of records" usually occurs when the number of records exceeds the limit specified in your current Data Integration product plan. To resolve this issue, you have a few options: Upgrade your plan to increase the ...

    • Tips for Managing Integration Queue Times

      Generally, when integrations start running, they are placed in a queue for execution before processing records begins. Integrations can be queued during server peak loads (such as at the beginning of every hour, e.g., 11:00, 12:00, etc.) when there ...

    • 📊 Skyvia Data Flow Logs Explained: The Reason Errors and Successes Aren't Shown by Default

      In Data Flow, tracking execution success or failure can be challenging due to the nature of row processing. Rows that fail in one component may succeed in another, complicating error detection. By default, Skyvia logs do not provide detailed error or ...

    • Salesforce Report exports only 2000 records

      Skyvia integrates with Salesforce via its API, inheriting both its features and limitations. One key limitation is the Run Report restriction, which limits data extraction to the first 2,000 rows of a report. For more details on this limitation, we ...

    • Account and Workspace Roles in Skyvia

      In Skyvia, we distinguish between account and workspace roles for seamless teamwork: 1. Account Roles The account admin, also known as the account owner, has full control over the account. They can manage subscriptions to Skyvia products, modify ...