Preventing Broken References: Smart Schema Change Warnings Needed

[#1]

Hi everyone,

One common issue I see often in Adobe Campaign is how risky it is to make schema changes—especially on core tables like nms:recipient.

Changing things like primary keys or data types can break references, cause data loss, or even crash the system.

It’d be super helpful if ACC had a Smart Schema Change Guard feature that could:

1. Warn you before making risky changes Show the full impact on related tables, logs, and workflows

2. Suggest safe migration steps or fixes

3. Allow easy rollback if something goes wrong

This would save a lot of headaches, prevent downtime, and help teams evolve their data models safely.

Has anyone else run into this? Would love to hear your thoughts or if you’ve found good workarounds!

Thanks!