Who has a blank stare even after 2 months in his new position? The answer is: a junior developer you hired and showed your ETL. I am talking ETL with hundreds of intertwined procedures. To be fair, a senior guy would have to chew on it too but they’re less likely to choke.
To greatly speed up the onboarding process and further speed up impact analysis we just launched a feature which allows you to track data lineage on a procedure level. Simply select a procedure name and within seconds you have a complete overview of what’s happening inside the script from data lineage standpoint.
Common tools like PL/SQL Developer or Microsoft SQL Management Studio help you to write stored procedures. However when you need to quickly understand what tables are used and how the tables are connected they offer little help. When you need to get onto the column level you are doomed to manual code analysis.
We have solved this through reverse engineering and automated analysis. You can try your single procedure or you can upload all of them through our app. You are just a couple of clicks away from having full documentation. Having a visual map of dependencies and data lineage allows for:
- Cutting times for impact analysis by 90%.
- Speeding up onboarding and mitigate the effect of brain-drain.
- Fulfilling audit requirements by tracking changes in DWH over time.
- Significantly reducing dependency on contractors and vendors.
- This neat visualisation should be in the toolbox in any data warehouse developer who is witlessly digging through stored procedures he and his teammates coded.