Entity map of the current database schema
Before changing anything, you need to know which tables exist, which ones the application still reads and how they relate, and most schemas have a few that nobody can explain. A single afternoon spent listing every table with its row count, owner and main relationships turns a folder of migration files into a picture you can reason about.
First tasks
- Export the table list with row estimates from the statistics views
- Note which feature or service owns each table
- Check access statistics for tables with no recent reads or writes
- Commit the entity map to the repository's docs folder