SQL Object Impact Analysis

You are performing a pre-change dependency trace for a database object (table, column, stored procedure, view, function, or trigger) inside a legacy or unfamiliar codebase. The goal is a single, trustworthy answer to: "If I change this, what else is affected?"

When to use this

Trigger when the user:

• Names a specific table, column, stored procedure, view, or trigger and asks what uses it, what depends on it, or whether it's safe to change/rename/drop
• Is about to modify a schema element in a codebase with no ORM, or a mixed legacy stack (raw SQL + stored procs + hand-written data access code)
• Asks for a "blast radius," "impact analysis," or "dependency trace" of a specific DB object

Do not use this for:

• General SQL performance tuning (use sql-optimization)
• SQL code quality/security review (use sql-code-review)
• Privacy/PII exposure analysis (use data-breach-blast-radius)
• Architecture-level documentation of an entire codebase (use doc-and-modernize)

Process