Changes to whether a field's change history is retained can be made easily within PCS and tables can have CDC-based tracking enabled or disabled as needed. It is recommended that change tracking modifications are made during the initial configuration of PCS or while performing system maintenance to avoid any impact to PCS users. The following are some scenarios that warrant a review of the change tracking settings and may result in updates to change tracking configurations:
PCS is upgraded - when installing new versions of PCS, new tables or fields may be added to the database. As a result, you may want to enable or disable fields from being tracked in the Field and UDF Customizations window. If your configuration of change tracking is enhanced with CDC, then you may want to enable CDC on the new tables and verify that CDC is not enabled on legacy tables.
New custom module or user defined field is created - when creating a new custom module or user defined field, new tables and fields are created and added to the database and set to be change tracked through simple triggers only, if change tracking is enabled. If your configuration of change tracking is enhanced with CDC, then you may want to enable CDC on the new tables. Or, depending on your company needs, you may want to disable the newly created fields from being tracked in the Field and UDF Customizations window.
Data usage changes - if your company's general usage of PCS evolves so that the tables involved in large operations changes, you may want to change which tables are tracked using CDC.
For instructions detailing how to update your simple trigger-based or CDC-enhanced change tracking configuration, refer Update Simple Trigger-Based Change Tracking or Update CDC-Enhanced Change Tracking , respectively.