exclude the tables for cloning

[akumbhare]

We are cloning prod to QA for upgrading to Zurich version.

Is it a good practice to exclude the below tables for cloning?

sys_properties,

sys_alias (Connection + Connection Alias),

discovery_credentials

[SanjivMeher]

Since there are no OOB exclude tables, I wouldn't use that.

Instead what we do is use "System Clone->Clone Definition->Preserve Data" to preserve data in target instance for certain properties which is instance specific.

Below are few examples.

[Roshnee Dash]

Hi @akumbhare ,

1. sys_properties -Exclude (or use Data Preservers)

   • QA usually has environment-specific values (URLs, MID servers, email, integrations, feature flags).

   • Cloning Prod properties can:

     • Trigger Prod integrations from QA

     • Break QA URLs / OAuth callbacks

     • Override upgrade-specific or testing flags

2. sys_alias - Exclude (or use Data Preservers).    

   • These are tied to:

     • Credentials

     • OAuth profiles

     • External endpoints

   • Cloning Prod aliases into QA can:

     • Cause QA to call Prod systems

     • Break existing QA integrations

3. discovery_credentials -Strictly Exclude 

   • Contains encrypted Prod credentials

   • Security & compliance risk

   • Credentials often differ between Prod and QA