Have the ability to persist the established relationships in SQLDBM even after you update the model from Snowflake and the DDL doesn't have the FK relationships in the code.
Since Snowflake doesn't enforce the FK constraint, ELT tools like Matillion do not have the ability to add the FK relationships into the DDL statement. If you are designing an EDW and utilizing this tool, when you extract your DDL from Snowflake to ingest into SqlDBM you lose all the relationships and have to manually go through the tables to re-establish them (very time consuming).
If you had an option to persist the relationships when the two tables still had the same FK fields, that would save hours of rework in SqlDBM.
Customer support service by UserEcho