---
title: "See what a SQL change will break before you merge - Atlan MCP Cookbook"
url: "https://atlan.com/mcp-cookbook/see-what-a-sql-change-will-break-before-you-merge/"
description: "Find every downstream consumer of a changed column or table before merging."
---

> Atlan is hosting Context Conference, bringing together the leaders and builders at the frontier of giving AI the context it needs to understand their business. It runs online on October 28, 2026, from 11:00 AM to 2:00 PM ET. Atlan co-founder Prukalpa Sankar opens and closes the day. Leaders from AstraZeneca, BNY and Verizon share why they invest in context and what they get from it. Registrants get early access to The AI Context Gap, a new study from MIT Technology Review Insights. Register: https://atlan.com/context-conference/

Recipe 6 in [The Atlan MCP Cookbook](https://atlan.com/mcp-cookbook/). Find every downstream consumer of a changed column or table before merging.

Use case: Change & fix data safely / Action: Look up / Persona: AI Builder, Data Engineer / Effort: Quick / Runs in: any AI tool

Requires Atlan MCP connected to your AI tool: [set up Atlan MCP](https://docs.atlan.com/product/capabilities/atlan-ai/how-tos/remote-mcp-overview).

## 1. The task

**Scenario.** Your PR renames user_id to customer_id in dim_users. The diff looks small, but the real risk is the views, dbt models, and dashboards that read dim_users and never show up in the diff. You want the full blast radius while you are still in review, not after the merge.

The ask:
- Every downstream view, table, and dashboard that references the table
- Each one's owner and certification status
- Enough to decide whether the change is safe to merge

Hero prompt: "I'm about to rename the user_id column to customer_id in the dim_users table. Trace the downstream consumers of dim_users - start with the direct ones and expand into the branches that matter - so I can assess the impact before merging."

Step by step:

1. Find the asset you're changing and confirm it has downstream lineage. Prompt: "I'm renaming [column] to [new name] in [table] - pull [table] and check what depends on it."
2. Trace its downstream consumers. Prompt: "Trace the downstream views, tables, and dashboards that read [table] - direct consumers first, then expand into the branches that matter."
3. Return the impact list with owners and certification. Prompt: "For each impacted asset, include its owner and certification status so I can decide what to test and who to warn."

## 2. What you'll give it

Required context:
- The table or column changing in the PR (user_id in dim_users)
- Lineage populated for that asset

Optional context:
- Whether to include indirect (multi-hop) consumers or only direct ones
- The certification bar that matters to you, so certified consumers stand out

## 3. What Atlan creates

Outputs:
- Every downstream view, table, and dashboard that references dim_users
- The owner and certification status of each
- A checkable impact list to paste into the PR

**Summary.** "I think this is safe" becomes a list you can check off. You see who to warn and what to test before merging, not after a dashboard goes blank.

**Read-only.** Nothing is written. This recipe only reads lineage and metadata, so it is safe to run against production from inside any review.

## 4. Follow-up prompts

- **Draft the warnings:** "For the certified consumers on that list, draft a short heads-up I can send their owners."
- **Focus the testing:** "Which of these consumers are certified or heavily queried, so I test those first?"
- **Widen the change:** "I'm also dropping legacy_flag in the same PR. Add its downstream consumers to the impact list."

## 5. Tips & troubleshooting

**Cook's note.** Paste this into your PR review. It turns "I think this is safe" into a list you can check off.

- Match the tool to the work. Run it in the AI tool you already review PRs in, so the impact list lands right next to the diff. Ask for the immediate downstream first and expand as needed; a full multi-hop pull can be huge.
- Automate or chain it. Chain it into CI: on a PR that touches a modeled table, post the impact list as a comment automatically.
- It only reads. Nothing is written back, so run it as often as you like, on any branch, without a change window.

## Related recipes

- [Warn downstream owners before a change lands](https://atlan.com/mcp-cookbook/warn-downstream-owners-before-a-change-lands/): Find every downstream consumer of a changing asset and warn their owners first.
- [Trace a broken dashboard to its root cause](https://atlan.com/mcp-cookbook/trace-a-broken-dashboard-to-its-root-cause/): Trace lineage upstream from a broken dashboard to find the source of wrong numbers.
- [Safely deprecate unused assets](https://atlan.com/mcp-cookbook/safely-deprecate-unused-assets/): Verify no active consumers exist, notify owners, then mark assets as deprecated.

[Browse all recipes](https://atlan.com/mcp-cookbook/) / [Set up Atlan MCP](https://docs.atlan.com/product/capabilities/atlan-ai/how-tos/remote-mcp-overview)