Skip to main content

We want to use cdc loging in sql server. Unfortunitly Thinkwise (deployment, creation part) wants to drop the indexes, stored procedure and function which are generated by sql server for the cdc loging. Is it posible in Thinkwise to ignore those indexes?


Example to activate cdc loging
EXEC sys.sp_cdc_enable_db

EXEC sys.sp_cdc_enable_table
@source_schema = N'dbo',
@source_name   = N'XXXXX',
@role_name     = N'UserRole',
@supports_net_changes = 1

SELECT * FROM Ocdc].cXXXXX_CT]

Error in thinkwise by deployment, creation part
INDEXES]
Cannot drop the index 'change_tables.change_tables_unique_idx', because it does not exist or you do not have permission.
Cannot drop the index 'change_tables.source_object_id_idx', because it does not exist or you do not have permission.
Cannot drop the index 'lsn_time_mapping.lsn_time_mapping_nonunique_idx', because it does not exist or you do not have permission.
Cannot drop the index 'dbo_account_CT.dbo_account_CT_clustered_idx', because it does not exist or you do not have permission.
Cannot drop the index 'dbo_account_CT.dbo_account_CT_idx', because it does not exist or you do not have permission.

Hi Ronald,

Of course we can exclude the CDC objects, but I expect you'll run into more problems when, for example, modifying or renaming tables in the upgrade script as we don’t officially support SQL Server’s change data capture feature. 

A feature that we are going to support (we’re working on it right now) is Temporal Tables, which has a lot of similarities and advantages over CDC. Would that be an option?

Reply


Terms & ConditionsCookie settings