As a retired DBA and someone who has had to pick up from others work, I suggest looking at the number of rows in a table as a very quick way of understanding importance. Second use those time stamps to understand when was the last updated records, on average how often are records changed, what is the oldest record in the table (Is this a historical record or a finance record with only the current fiscal year). The most important thing that can be done is not listed above and the real answer is ask the people who use the database. Talk to the people who finance the cost of the computers and support. If you know what the industry in general most businesses will be roughly the same so look on the internet and see what the competitors are doing.
How about something like https://github.com/k1LoW/tbls ? Might be quite helpful.
As a retired DBA and someone who has had to pick up from others work, I suggest looking at the number of rows in a table as a very quick way of understanding importance. Second use those time stamps to understand when was the last updated records, on average how often are records changed, what is the oldest record in the table (Is this a historical record or a finance record with only the current fiscal year). The most important thing that can be done is not listed above and the real answer is ask the people who use the database. Talk to the people who finance the cost of the computers and support. If you know what the industry in general most businesses will be roughly the same so look on the internet and see what the competitors are doing.