How Tadabase stores your data

For developers who know SQL: how tables, fields, connections, rollups and equations map to database ideas, plus the limits and where files are stored.

  • Verified Nov 17, 2026
  • Classic builder

On this page
  1. From SQL to Tadabase
  2. When calculated values are worked out
  3. Limits
  4. Where files are stored

If you know relational databases, most of Tadabase will feel familiar. This page maps Tadabase's names to the SQL ideas you know, explains when calculated values are worked out, and lists the limits that matter when you design a data model.

From SQL to Tadabase #

In SQLIn TadabaseNotes
TableData tableCreated in the Data Builder. See Create and manage data tables.
ColumnFieldEach field has a type (text, number, date, file and so on) and a slug such as field_36, which is its name in the API.
Row and primary keyRecord and record IDEvery record has an id. The API shows IDs, and table IDs, as short encoded strings such as DVWQWRNZ49.
Foreign key and JOINConnection fieldLinks records in one table to records in another. A record can show fields of the record it is connected to without a query. See Connect tables with connection fields.
COUNT, SUM, AVG, MIN, MAX, GROUP_CONCAT over child rowsRollup fieldSummarizes the connected records of each record, optionally only those that match conditions. See Rollup field.
Computed columnEquation and formula fieldsCalculate a value from the record's other fields, such as a total or a formatted date. See Equation.
A value worked out when you read itDynamic fieldShows a value built from a template each time it is displayed; nothing is saved. See Dynamic field.

Through the API, a connection field comes back under its slug as a list of connected record IDs, and again with _val added, with each ID and its display value. See Field types reference.

When calculated values are worked out #

Equation, formula and rollup values are saved with each record, so you can sort and filter by them like any other field. They are recalculated when the record is saved.

  • By default, an API call that saves a record recalculates its equations before it answers. Your call can skip that, or have it done in the background so the API answers sooner; the values then lag behind for a moment. See Formulas and equations.
  • You can recalculate a whole table, or one field, through the API with a key that has Allow Formula Runs on.
  • Turning a rollup's Enable switch off stops it recalculating; the values already saved stay as they are.
  • To find calculations that slow your saves down, use Formula Performance. See Speed up slow formula fields with the query optimizer.

Limits #

LimitBusiness StarterBusiness GrowthBusiness ProBusiness Elite
Tables per app300300300300
Fields per table300300300300
Records per account30,000125,000250,000500,000
File storage5 GB10 GB50 GB100 GB

Older plans can have other limits; Pricing shows the current ones. A table with many long fields can also hit the size limit of a database row; see Shrink a table's columns with Optimize Datatable. Through the API, a list call returns at most 100 records per page.

Where files are stored #

Files uploaded to file, image and attachment fields are stored by Tadabase and count toward your plan's file storage. On plans that include it, you can store them in your own Amazon S3 bucket or Dropbox account instead, in Settings > File Storage Settings. See File storage settings.

Was this page helpful?

Something wrong or missing on this page? Tell us.