Truncate or rebuild
Keep the definition, or replace the table outright.
Replicate Facebook Ads into Azure SQL with Polytomic so Meta spend is queryable in T-SQL. When a report needs replacing wholesale, truncate keeps the table definition and reloads it, while rebuild drops and recreates the table entirely.
Keep the definition, or replace the table outright.
Each one lands as its own Azure SQL table.
Seven day default. Widen it before the first load.
Polytomic is bi-directional by default, so you can move data the other way just as easily.

Jonathan Krangel
VP Global Head of Revenue Operations
“Polytomic handles so many ETL and sync jobs at Cursor. They are a true partner to us.”
Follow these simple steps to connect Facebook Ads with Azure SQL in minutes
Connect Facebook Ads
Connect Azure SQL
Create sync
Enable sync
Connect Facebook Ads to Polytomic with OAuth, or with your own Meta system user token.
Connect Azure SQL to Polytomic with server, database, and SQL authentication credentials.
Sync data in either direction between Facebook Ads and Azure SQL. Choose the source data and destination objects for the direction you need.
Map the fields, choose the sync schedule and behavior, then save and enable the sync.
Get answers to common questions about the integration process
Sync data in either direction between Facebook Ads and Azure SQL.
Use both integrations' source and destination capabilities in one managed sync workflow.
Enterprise encryption and security protocols ensure your data remains protected.
Get up and running in minutes with our step-by-step integration guide.