I’ve been testing a new feature in SSIS Catalog Compare‘s catalog browser. I call it “values everywhere.” What do I mean by values everywhere? In the browser shown above, please note the reference mapping of the ConnectionString property for the package connection manager in SimplePackage.dtsx. Each Reference is listed as a child node of the reference mapping, and the values of each reference-mapped Environment Variable appears as a sub-node of the Reference.
My intent here is to surface related configurations metadata at the location where said metadata is consumed. I think that makes sense, reduces right-clicking, and is more intuitive.
I also surface reference-mapped environment variable values in the Package and Project References nodes.
As before, the environment variable values remain available (and update-able) in the Environments node.
I welcome your feedback. What do you think?