BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
7/20/2023
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2016 Service Pack 1
SQL Server 2017 on Windows (all editions)
SQL Server 2017 on Linux (all editions)
SQL Server 2019 on Linux
SQL Server 2019 on Windows
build lower than 15.0.4063.15
15.0.4063.15
Assume that you use the Always Encrypted feature of Microsoft SQL Server to encrypt a column in the table. You now enable the Change Data Capture (CDC) for this table, and the encrypted column is not included in the captured_column_list. In this scenario, when you try to use the system stored procedure sp_cdc_disable_table to disable CDC for the table, you may receive an error message that resembles the following: Msg 22833, Level 16, State 1, Procedure sp_cdc_disable_table_internal, Line LineNumber [Batch Start Line LineNumber] Could not update the metadata that indicates table TableName is not enabled for Change Data Capture. The failure occurred when executing the command 'sp_cdc_disable_table_tranx'. The error returned was 11430: 'Cannot enable change data capture on column 'ColumnName'. Change data capture is not supported for encrypted columns.'. Use the action and error to determine the cause of the failure and resubmit the request.
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 7 for SQL Server 2019 Cumulative Update 1 for SQL Server 2017 Cumulative Update 8 for SQL Server 2016 RTM Cumulative Update 5 for SQL Server 2016 SP1