April 10, 2018 at 8:24 am
SQL Server Default Instance: CDC enabled database SQL Server Enterprise 2014 SP2-CU11 [CDC Source table]
SQL Server Named Instance: SQL Server 2016 Enterprise SP1-CU8 [destination tables]
Visual Studio 2015 with SSDT 17.4 (14.0.61712.050)
We are encountering an issue using CDC tasks (CDC Control Task/CDC Source/CDC Splitter). When using CDC Source SSIS task, we receive an error trying to execute: “Select [__$start_lsn], [__$operation], …. , zip, [__$command_id] from [cdc].fn_cdc_get_net_changes_dbo_Assistants]…Reason – Invalid column name ‘__$command_id’
After applying SQL CU, the __$command_id column was added to our cdc tables, however, the cdc functions fn_cdc_get_<all, net>_changes_dbo_xxxxx do not contain a __$command_id column.
Is there a fix for this issue? The only fix that we have seen in blogs is to update the system cdc functions which isn't really a fix and should not be changing system cdc functions to make this work.
Thanks in advance.
April 12, 2018 at 2:27 pm
ericwenger1 - Tuesday, April 10, 2018 8:24 AMSQL Server Default Instance: CDC enabled database SQL Server Enterprise 2014 SP2-CU11 [CDC Source table]
SQL Server Named Instance: SQL Server 2016 Enterprise SP1-CU8 [destination tables]
Visual Studio 2015 with SSDT 17.4 (14.0.61712.050)We are encountering an issue using CDC tasks (CDC Control Task/CDC Source/CDC Splitter). When using CDC Source SSIS task, we receive an error trying to execute: “Select [__$start_lsn], [__$operation], …. , zip, [__$command_id] from [cdc].fn_cdc_get_net_changes_dbo_Assistants]…Reason – Invalid column name ‘__$command_id’
After applying SQL CU, the __$command_id column was added to our cdc tables, however, the cdc functions fn_cdc_get_<all, net>_changes_dbo_xxxxx do not contain a __$command_id column.
Is there a fix for this issue? The only fix that we have seen in blogs is to update the system cdc functions which isn't really a fix and should not be changing system cdc functions to make this work.
Thanks in advance.
That bug has been a bit "all over the place" in terms of what builds it affects and what scripts fix it. That fix with adding the column caused other issues. This one you may want to take a look at and test:
CDC functionality may break after upgrading to the latest CU for SQL Server 2012, 2014 and 2016
This post is fairly recent - read the comments:
SQL Server CDC Invalid column name __$command_id
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply