Track and Record Data Changes with Change Data Capture (CDC) in Azure SQL | Data Exposed

[@MrMonday1000percent]

Excellent demo and presentation. At 12:10 to 12:30 there is a small error in wording, the retention parameter value is actually minutes not seconds. The default being 4320 minutes which is 72 hours which is 3 days. As always check the docs as this may change in future versions (hopefully not though!).

[@daniyalahsan6166]

Is there a way to use CDC to upsert values into a table based on a primary key? if so can someone please advise or share a link if you have one. Thanks

[@paulantohe3783]

Frumoasa Mara :D 😁

[@allenbabu4336]

I have installed sql server 2019 in Linux with multiple databases created on it. I have multiple tables across different databses with CDC enabled. But the SQL server gets hanged very often due to this cdc. KIndly let us know, if Linux having any issue with cdc enabled.

[@sintetico82]

Can you prived more concrete examples about these scenarios "propagate changes to downstream subscriber" and "event-based programming that provides instantaneous responses based on data change". I would like to connect SQL Server 2019 CDC events to a message broker like RabbitMQ but look like there isn't anything already developed.

[@abhimantiwari]

Multiple other Microsoft technologies such as Azure Data Factory can be used to move CDC change data to other destinations (e.g., other databases, data warehouses). Also, other third-party services also offer streaming capabilities for change data from CDC. For instance, Striim and Qlik offer integration, processing, delivery, analysis, or visualization capabilities for CDC changes. Debezium can also be used to process CDC changes in real-time over various binders such as RabbitMQ, Azure Event Hub, Apache Kafka etc.

[@jordannyc2769]

Any way to use elastic/kibana against CDC to monitor stored procedures or any scheduled sql inserts/updates ?

[@kosmologic6007]

I did kafka streams & connect cdc on sql monitoring by API using static monitors in New Relic. Works fine on prod.

[@harry5472]

When to use CDC vs Database Ledger? If your requirements are just table auditing.

[@abhimantiwari]

CDC is a widely used feature by a wide range of customers for a variety of purposes as mentioned below, but not limited to: 1. Tracking data changes for auditing 2. Recording data changes on source database and integrating with other services (e.g., Azure Data Factory) to stream these changes to other destinations 3. Performing analytics on change data   Azure SQL DB ledger uses the power of blockchain with the simplicity of SQL. It makes data in SQL tamper-evident through cryptography. Provides a historical record of all changes, verified through cryptographic proofs.

[@samuelgit]

Hi, How I can identify which user did each change using CDC?

[@abhimantiwari]

Hi Sam, CDC doesn't record user identity performing the change. If you wish to store user identity, you will need to handle with custom code logic.

[@walterlonso]

Hi, Is this feature delivered in all regions? for example China?

[@marasteiu6854]

Hi! Yes, it's in public preview worldwide.

[@DanielWillen]

@@marasteiu6854 When is it leaving preview do you think?

[@samuelgit]

@@marasteiu6854 do you know how to identify which user did the change? do you have some documentation please?

[@abhimantiwari]

@Walter Alonso Yes

[@sconnell194]

👍

[@hydtechietalks3607]

why does Microsoft always get a Non Inglis speakers .. all the complexity lies in there 🤣

[@praveennakka2021]

Not a good presentation guys sorry.... Step up please