August 19, 2020 at 6:31 pm
Running SQL 2016 Standard SP2 CU14 (the most recent version)
I see a lot about this issue and best i can tell its just a bug that Microsoft isn't going to fix. It seems there are different opinions of what to do.
The wrapper function creates scripts for other functions that will return change data based on start/end times. But they don't build because the table valued function they select from doesn't return the __$command_id. That field is in there but only used for sorting.
Msg 207, Level 16, State 1, Procedure fn_net_changes_ft_fsdaily, Line 38 [Batch Start Line 5]
Invalid column name '__$command_id'.
Does anyone know what is the proper work around for this?
August 20, 2020 at 7:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
August 25, 2020 at 5:52 am
The solution to get the jobs going again is dropping CDC on all tables that have it enabled (using cdc_disable_table), dropping the capture agent job and then re-enabling tables for CDC (using cdc_enable_table). Unfortunately, this causes data loss in the _CT system tables unless you copy it off to another persistent table mcdvoice.com
February 27, 2021 at 12:04 pm
This was removed by the editor as SPAM
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply