Do New Tables Impact DPU Consumption?

When you add a new table or connection to your BEEM workspace, it may affect your DPU consumption depending on timing and context. This article explains the rules around new table consumption and how to check your usage.

When Is a Table Considered "New"?

A table is considered new when it is included in your workspace for the first time. This includes:

• Creating a new connection to a source system
• Selecting a previously unselected table within an existing connection
• Re-enabling a table that was excluded during the initial connection setup

Adding Tables During a Connection Trial

Every new connection includes a 14-day trial period. During this trial:

• The initial sync and all incremental updates are free (no DPU consumption)
• Adding new tables to the connection does not extend the trial period

Adding Tables After a Connection Trial

Once the trial has ended:

1. Initial sync of a new table counts toward your free DPU allocation
2. Incremental syncs after the initial load count toward paid DPU consumption

Adding Columns to an Existing Table

When a new column is added to a table that has already been synced, BEEM may detect a change on every existing row. This means the next sync could consume DPUs proportional to the full table size, not just newly inserted rows.

Re-importing a Table

When you re-import a table that was previously synced, only new and changed rows consume DPUs. Unchanged rows are not reprocessed.

How to Check Whether a Table Has Been Synced

1. Navigate to the Datalake section
2. Click on the source name for the connection you want to inspect
3. Review the list of tables — you can see which tables have been synced and their status

For questions about your consumption or plan limits, contact [email protected].