konveyor/tackle-data-gravity-insights

Explore extending Schema2Graph capabilities

rofrano opened this issue · 1 comments

As a Application Architect
I need the ability to analyze constraints, triggers, and other schema artifacts
So that I get a complete picture of the relationships between tables

Details & Assumptions

  • Add constraints to the graph to show how some columns are being used
  • Add indexes to the graph to indicate columns used in queries
  • Add triggers and field procedures to the graph to understand how updating columns affect other columns
  • Should we add stored procedures to the graph? What would that look like?
  • Should we process materialized views?

Feel free to add more details as you learn more

  • Create trigger in ddl and run through s2g
  • Collect trigger examples (https://ibm.box.com/s/cqh7h6yksfwjypjl62lv273h5354vs9)
  • Write a parser to extract the table names in the trigger
  • Annotate the table names with trigger (trigger_update, trigger_insert) in graph
  • Contact CIO office for example schemas