The JADE 2022 release meets tomorrow’s business demands.
If Jade RPS mapping could include details of enabled SQL CDC tables, then additional actions/tests could be completed at different stages during deploys and data pump restarts.
Example:
When a SQL table is dropped by jade, and the SQL table is CDC enabled, the corresponding CDC system table is also dropped automatically.
Restarting the data pump without reenabling CDC on the newly created table would create issues in the consuming service / application.
If the data-pump application had access to a list of pre-defined tables that were CDC enabled then these could be checked on initialisation and error, or enabled them automatically.
could we introduce conditional alter script options.
Don't readd Primary keys on Jade dropped tables.
If Table is CDC enabled.
Any reason why we need to reapply the Primary Key. Could this be optional?
When creating the new table "Customer_Account_Detail" we get the following message.
The unique index 'PK_Customer_Account_Detail' on table '[dbo].[Jade_Dropped_15February2024@125201_Customer_Account_Detail]' is used by Change Data Capture.
update - If jade renames a table as part of the RPS mapping changes as a backup.
IE 'Jade_Dropped_15February2024@125201_Customer_Account_Detail'.
Jade also drops and reapplies any Primary keys on the backup table.