Keyed records upsert
Issues and pull requests merge on ID.
Replicate GitHub into Azure SQL with Polytomic so repository activity is queryable in T-SQL. Keyed records like issues and pull requests upsert on their primary key, while unkeyed event style data is appended rather than merged.
Issues and pull requests merge on ID.
Unkeyed rows accumulate rather than merge.
Bodies land in NVARCHAR(4000).

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 GitHub with Azure SQL in minutes
Connect GitHub
Connect Azure SQL
Create sync
Enable sync
Connect GitHub to Polytomic with OAuth, then select the repositories you want to sync.
Connect Azure SQL to Polytomic with server, database, and SQL authentication credentials.
Sync data from GitHub to 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 from GitHub to 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.