Edit

Share via


Connectors for Copy Job

With Copy job, you can move your data between cloud data stores or from on-premises sources that are behind a firewall or inside a virtual network using a gateway.

Copy job supports the following functionalities:

Copy job sources and destinations

The following table shows which connectors are supported as sources and destinations in Copy job, and whether they support different read and write modes.

  • Read - Full load: Read the entire data from the source.
  • Read - Incremental load (watermark based): Read only the changed data from the source using a watermark column.
  • Write - Append: Add new data to the destination without affecting existing data.
  • Write - Override: Replace existing data in the destination with new data.
  • Write - Merge: Combine new data with existing data in the destination based on a specified key.

For more information about each of these modes, see the copy job overview.

Connector Source Destination Read - Full load Read - Incremental load (watermark based) Write - Append Write - Override Write - Upsert
Amazon RDS for Oracle
Amazon RDS for SQL Server
Amazon S3 N/A
Amazon S3 compatible N/A
Azure AI search
Azure Blob Storage N/A
Azure Cosmos DB for MongoDB
Azure Cosmos DB for NoSQL
Azure Databricks
Azure Data Lake Storage Gen2 N/A
Azure Data Explorer
Connector Source Destination Read - Full load Read - Incremental load (watermark based) Write - Append Write - Override Write - Upsert
Azure Files N/A
Azure MySQL
Azure PostgreSQL
Azure SQL DB
Azure SQL Managed Instance
Azure Synapse Analytics
Azure Tables
Cassandra
Dataverse
Dynamics 365
Connector Source Destination Read - Full load Read - Incremental load (watermark based) Write - Append Write - Override Write - Upsert
Dynamics AX
Dynamics CRM
Fabric Lakehouse file N/A
Fabric Lakehouse table
Fabric Warehouse
Folder N/A
FTP N/A
Greenplum
Google BigQuery
Google Cloud Storage N/A
Connector Source Destination Read - Full load Read - Incremental load (watermark based) Write - Append Write - Override Write - Upsert
HTTP N/A
IBM Db2 database
Informix
MariaDB
Microsoft Access
MongoDB
MongoDB Atlas
MySQL
ODATA
ODBC
Connector Source Destination Read - Full load Read - Incremental load (watermark based) Write - Append Write - Override Write - Upsert
Oracle
Oracle Cloud Storage N/A
PostgreSQL
Presto
REST N/A
Salesforce
Salesforce service cloud
SAP BW Open Hub
SAP HANA
SAP Table
Connector Source Destination Read - Full load Read - Incremental load (watermark based) Write - Append Write - Override Write - Upsert
SharePoint Online list
ServiceNow
SFTP N/A
SQL Server On-premises
Snowflake
Teradata
Vertica

Note

The ODBC connector with native incremental copy capability only works for Microsoft SQL family data stores, including:

  • Amazon RDS for SQL Server
  • Azure SQL DB
  • Azure SQL Managed Instance
  • Azure Synapse Analytics
  • Fabric Warehouse
  • SQL Server On-premises

CDC Replication (Preview)

Change data capture (CDC) in Copy job enables automated replication of changed data (including inserted, updated, and deleted records) from a source to a destination. This table outlines the connectors that support CDC replication in Copy job, including their capabilities for reading CDC data, writing with merge (SCD Type 1), and writing with SCD Type 2 for full history tracking.

For more information about using CDC replication in Copy job, see Change data capture in Copy job.

Connector Source Destination Read - CDC Write - Merge Write - SCD Type 2
Azure SQL DB
Azure SQL Managed Instance
Fabric Lakehouse table
Google BigQuery
On-premises SQL Server
SAP Datasphere Outbound for ADLS Gen2
SAP Datasphere Outbound for AWS S3
SAP Datasphere Outbound for Google CloudStorage
Snowflake
Oracle
SQL database in Fabric (Preview)
Fabric Data Warehouse

Note

SCD Type 2 in Copy job is currently in preview. When doing CDC replication from Snowflake or Oracle sources, SCD Type 2 isn't supported yet. If your destination database already has existing schema created by yourself, SCD2 can't be supported.

Automatic table creation and truncate on destination

Copy job can automatically create tables in the destination if they don’t already exist. You can also optionally truncate destination data before the full load, ensuring their source and destination are fully synchronized without duplicates. This table outlines the connectors that support automatic table creation and truncate on destination in Copy job.

For more information about these features, see the copy job overview.

Connector Automatic table creation Truncate destination before full load
Azure SQL DB
Azure SQL Managed Instance
Azure Synapse SQL Pool
Fabric Lakehouse table
Fabric Warehouse
On-premises SQL Server
Oracle
Snowflake
SQL database in Fabric (Preview)