All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
Allow the ETL DDL objects (views, tables, etc) to be captured over time such that a history of the changes are available.
This serves two purposes - simple BACKUP for when you save a rule and need to revert back to a previous version (but don't want to involve a DBA for such a simple thing).
But it also enables the RATE OF CHANGE metrics because we can now see how many and how often rules are being changed in response to design and mapping changes.
Ideally this should capture all Developer created SQL - including working dbs, source, target, and construct.
John Munkberg
