Every data engineer can point to countless hours lost mapping all the downstream dependencies of a column. All because they need to know if it’s safe to delete. Or worse: because they already deleted it and broke everything.

This is a very common problem for data teams. Needless to say that it shouldn’t be. Not only is it incredibly boring, it’s also a huge waste of a highly skilled engineer’s time.

As a data engineer, you should know right away how something as innocent as adding a column to a table will impact other people in your organization. Or maybe you’re tempted to drop an unused table, only to find that perhaps it wasn’t exactly as unused as you’d expected.

Alvin solves that problem for you in a just few clicks with our impact analysis tool, as our co-founder Dan explains in this quick video:

Understand your data

Yes, Alvin’s impact analysis tool will show you what you’re about to break, before you break it. Which is great. But there’s more to it than that.

Because breaking things isn’t ideal, but at least when you know it happened, you can accept it, pick up the pieces, and move on with your life.

Stale and low-quality data, on the other hand, is the silent killer — you won’t see what’s coming until it hits the fan. Picture this: someone at your company realizes they’ve been using stale data to base important high-level decisions on. Plot twist: that someone is the CFO. It’s awkward.

You run for the hills, assume a new identity, and live out the rest of your days as a humble goatherd.

All of this could have been avoided if the data team had only known what would happen to each table, column and job whenever something changed!

Save time. Save money.

With Alvin’s impact analysis tool, you can see what jobs will break and what data will get stale. You’ll get warnings about changes to data quality, including different types and levels of threats.

And now, when you can fully predict what is going to happen before it happens? No more precious engineering hours wasted digging before deleting, no more putting out fires after something inevitably still breaks (sometimes the engineers).

We did the math and there’s literally no reason for a person to manually map these downstream dependencies when a tool can do it without slowly dying inside.

That tool is Alvin, by the way. In case that wasn’t clear. Sign up and try it out 😎

And if you don't wanna miss any future feature announcements, subscribe to our newsletter.