Question 1

How much data can I put in a base?

Accepted Answer

Less than you would put in a table. Airtable enforces per base record limits and rate limits its API per base, so the practical approach is to sync a filtered view: the accounts a team is working this quarter, not every account you have ever had.

Question 2

Will a second run duplicate records?

Accepted Answer

Not if you nominate a key field. Polytomic upserts on the field you choose, so a rerun updates the existing record. Without a key it has nothing to match on, which is exactly where duplicates come from.

Question 3

Which Airtable field types can I write to?

Accepted Answer

Single line and long text, number, checkbox, date, single and multiple select, and linked records. Select fields need the option to already exist in Airtable, so create those before the first run rather than after it.

Question 4

Can people edit the records once they arrive?

Accepted Answer

They can, and the next sync will overwrite whichever fields Polytomic manages. The usual pattern is to leave a few columns unmapped for human notes, so those edits survive every run.

Question 5

Is this ETL or reverse ETL?

Accepted Answer

Reverse ETL. The data is moving from your database out into a tool people work in, which is the opposite direction from the ETL that fills a data warehouse.

Sync Azure SQL to Airtable

Sync Azure SQL to Airtable with Polytomic

Filter at the source

Upsert on a key field

Field types respected

Or sync Airtable to Azure SQL

Trusted by businesses worldwide

Step-by-step integration guide

Connect Azure SQL in Polytomic

Connect Airtable in Polytomic

Create a sync between Azure SQL and Airtable

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Azure SQL with Airtable?