Change Impact Analysis
Shows which objects a change touches and which other objects depend on them, through foreign keys, views, triggers, routines, indexes and the links each engine has.
What you provide
- Connection (required).
- Script (required).
How it works
- The objects the script changes are collected the same way the blast radius collects them: tables and views in SQL, collections in MongoDB scripts, key patterns in Redis commands, labels in Cypher and indexes in Elasticsearch requests. A name without a schema is matched to the object the database holds, otherwise to the connection's default schema.
- The connection's dependency graph is walked from those objects, as for the blast radius on a script in Migration Scripts: views, foreign keys, triggers, routines and indexes on the relational engines, views and indexes on MongoDB, materialized views and indexes on Cassandra, relationships and indexes on Neo4j, and aliases on Elasticsearch. Every dependent object is listed with how it is linked. If part of the graph cannot be read, or the walk stops at its node limit, an advisory says so.
- The AI model rates each dependent object's risk and writes a short summary.
What you get
The directly affected objects, each dependent object with how it is linked (Foreign key, View, Trigger, Function, Partition, Index, Relationship or Alias) and its risk (Low, Medium or High), and a summary.