Piggy backing off my other idea linked below, I am suggesting that similar to how magic ETLs can be set to refresh only when chosen datasets have been updated, port that same functionality over to views, so that a view's metadata doesn't register as updated until all the source objects have updated. In the example below the view "updates" 4 times a day when each of the source tables update, this triggers downstream dependencies to then also refresh 4 times a day. If we can apply a rule to the view to say don't update until all source objects have updated, this would be a significant resource savings. This one dependency alone costs ~1,460 credits a year (ETL runs each time the view updates, which is each time a source table updates, 365*4), over a thousand more credits then necessary.
