Exclude "net-zero" changes (important for data warehouses)
Some processes may issue DDL statements which will have a net-zero effect, it would be useful to exclude them. Here are some example:
- stored procedure or SSIS package drops table and recreates it back exactly how it was including indexes.
- a script drops indexes on staging table and then create them back, so net effect is zero.
You may find a lot of such processes in Data warehouses. If you review the changes in the dashboard, then you see message "The changes made to this object can't be displayed. The object may have been rolled back." and a line for each execution. So they pollute the dashboard even though there are not any material changes to the object.
Object filters are not appropriate in this case, because they completely exclude objects from monitoring. And if somebody makes any change to such an object, for instance adds a column to the index, then such change won't be detected.
It would be great to have an option to exclude net-zero changes, or at least to have that option on object filter, to exclude only net-zero changes.
I completely agree. Need a way of not ignoring net zero changes. Muddies the waters.
Chris J commented
In case someone makes a change and then reverts to a known state, Dashboard still regards this as "drift". It would be good to be able to choose to ignore this on a per-pipeline basis to avoid Just Click Yes Syndrome.