[kgilpin]

The approach that I am taking is to narrow the ERD to a specific context, such as a single HTTP server request route. When the specific tables and relationships are rendered for just that route, a manageable amount of data is presented.

This approach also provides metadata that can be used to figure out which tables are being used where in the code, and vice versa.

Context is king!

[thisisbrians]

I have been thinking along these same lines as our architecture has gotten more complex over the years. I've toyed with the idea of adding some sort of comment syntax into our codebases that would allow some level of automation around this idea. Auto-generation might work quite well given the limited context, to your point.