If you delete a CDC-Enabled database on a SQL Managed Instance using the Azure Portal: The 'capture' and 'cleanup' jobs remain and can be seen the Job Activity Monitor The CDC Job records remain in the 'msdb.dbo.cdc_jobs ' table, with a [dbName] value of NULL When deleting / dropping a CDC-Enabled database on a SQL Managed Instance using SSMS and the Azure Data Studio the jobs are correctly removed from the Job Activity Monitor and 'msdb.dbo.cdc_jobs ' table.

Bug in Azure Portal When Deleting a CDC-Enabled Database From a SQL Managed Instance

sguidos 10

If you delete a CDC-Enabled database on a SQL Managed Instance using the Azure Portal:

The 'capture' and 'cleanup' jobs remain and can be seen the Job Activity Monitor
The CDC Job records remain in the 'msdb.dbo.cdc_jobs ' table, with a [dbName] value of NULL

When deleting / dropping a CDC-Enabled database on a SQL Managed Instance using SSMS and the Azure Data Studio the jobs are correctly removed from the Job Activity Monitor and 'msdb.dbo.cdc_jobs ' table.

Mahesh Kurva 1,785 Reputation points Microsoft Vendor

2025-01-17T00:55:20.8433333+00:00

Hi @sguidos,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

Thank you for bringing this issue to our attention. We understand that when deleting a CDC-enabled database from a SQL Managed Instance using the Azure Portal, the ‘capture’ and ‘cleanup’ jobs remain visible in the Job Activity Monitor, and the CDC job records in the ‘msdb.dbo.cdc_jobs’ table show a NULL [dbName] value.

When using SQL Server Management Studio (SSMS) or Azure Data Studio, the jobs are correctly removed, which indicates that the issue is specific to the Azure Portal.

We are reaching out to the internal team to get more information related to your query and will get back to you as soon as we have an update.

Share via

Bug in Azure Portal When Deleting a CDC-Enabled Database From a SQL Managed Instance

Your answer