Automatic Schema Visualization always miss the biggest point.
When you generate visualization, you should only show key table and key fields within the table and hide all the helper, secondary fields and tables.
In an LLM world this should be easy for LLMs to pick out key tables and fields and only display those
Some fields are important for HR, others for Security, others for BI. Gotta have different visualizations for everyone.
LLM here would be like another person or another team, that decides what's important for me, what I should see and what I should not. Might work, but I'd rather see the full picture and decide myself.
Why would you need an LLM to do this? The whole point is that SQL describes it's own relationships. You literally have everything you need out of the box.