Azure-docs: Any alternatives to achieve Change Data Capture when storing data on the cloud?

[weitzhandler]

Hi,
We're developing a new app the CDC is mandatory, but we would like to store the data on the cloud. Since Azure SQL doesn't support CDC we're looking for alternatives. NoSQL is also considerable, but we'd prefer to work with EF Core.
Any ideas?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3fb7dad4-ff47-5b16-e8ee-0a5e037ea20f
• Version Independent ID: 98ec245b-bd8f-bd96-ec6d-0048599246fa
• Content: Azure SQL Database feature comparison
• Content Source: articles/sql-database/sql-database-features.md
• Service: sql-database
• GitHub Login: @jovanpop-msft
• Microsoft Alias: jovanpop

[MarileeTurscak-MSFT]

@weitzhandler
Thanks for your feedback! We will investigate and update as appropriate.

[weitzhandler]

We can use SQL Server VM but that would be notably more expensive, anyway, worth updating the docs with this.
Anyway thanks for the update.

[Mike-Ubezzi-MSFT]

@dcbrown16 The Change Data Capture (CDC) is supported with Azure SQL Database Managed Instance. I want to bring this to your attention, as it seems that you have overlooked this or are not aware that it is an option. Please advise... Azure SQL Database Managed Instance

[weitzhandler]

I'm considering Temporal Tables too.
Still checking out what each of them does and what's right for me.
Thanks for your reply @Mike-Ubezzi-MSFT, I didn't know about SQL DB Managed Instance. Maybe this should appear in the title of the docs:

[Mike-Ubezzi-MSFT]

@weitzhandler Although not totally incorrect, the Applies To: can be misleading when dealing with functionality between Single/Elastic Pools and Managed Instance. The following: SQL Server feature support in Azure SQL Database has a more clear distinction.

Azure SQL Database has three deployment options (with exception to SQL in an Azure VM):
Single Instance
Elastic Pools (Database Pools)
Managed Instance

The Managed Instance option is almost a full featured (on-premise) deployment. As with all things cloud, there is almost constant progression. Thank you very much for your feedback. I am making the content author aware of this @CarlRabeler. Thank you!

[CarlRabeler]

@weitzhandler thanks for bringing this to my attention - updating the docs now