Skip to content

Commit 516b229

Browse files
Merge pull request #216977 from kromerm/cdc2
Update concepts-change-data-capture.md
2 parents dbdad59 + 4eae927 commit 516b229

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/data-factory/concepts-change-data-capture.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,8 @@ When you perform data integration and ETL processes in the cloud, your jobs can
2828

2929
The changed data including inserted, updated and deleted rows can be automatically detected and extracted by ADF mapping data flow from the source databases. No timestamp or ID columns are required to identify the changes since it uses the native change data capture technology in the databases. By simply chaining a source transform and a sink transform reference to a database dataset in a mapping data flow, you will see the changes happened on the source database to be automatically applied to the target database, so that you can easily synchronize data between two tables. You can also add any transformations in between for any business logic to process the delta data. When defining your sink data destination, you can set insert, update, upsert, and delete operations in your sink without the need of an Alter Row transformation because ADF is able to automatically detect the row makers.
3030

31+
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE5bkg2]
32+
3133
**Supported connectors**
3234
- [SAP CDC](connector-sap-change-data-capture.md)
3335
- [Azure SQL Database](connector-azure-sql-database.md)

0 commit comments

Comments
 (0)