But why might this be valuable for me?
Most dependency analysis tools that exist scan the metadata created by your data platform and report to you on your data objects (things like "View X was created from Table Y"). This gives you a sense of the dependent relationships present among your tables and views, but what about other objects? In most data platforms, there will exist a wide variety of objects beyond tables and views such as procedures and functions. This extends even to platform specific objects (for example, in Snowflake you may have a stage, file format, session policy, role, and a host of others). How do you get an idea of the dependent relationships present in your procedural code?
With BlackDiamond Studio, that's how. The dependency analysis capabilities of BlackDiamond Studio are not limited to tables and views. By utilizing our secret sauce of "code understanding" that can scan, analyze, and build semantic models of a variety of code languages, you can see what tables and functions a procedure may be dependent on. You can see all of the views that call a specific function. You can see how a unique script written in Python or another language depends on certain objects in your database and vice versa (what objects depend on proprietary scripts to be run). For the first time, you can get a real sense of how any code you have touches your database with BlackDiamond Studio.