How do you analyze 100+ database tables ?

[SONYFX]

If you are a new team member of a project, and the database tables aren't well documented, how do you analyze 100+ database tables? What tool(s) do you want to use?

 

[Xyo II]

Patience.

 

[mdchesne]

analyze them for what? content? accuracy? order?

 

[SONYFX]

Analyze the relationship between tables.

 

[iotone]

i think depending on the DB software, and given foreign key constraints have been established, you might be able to automatically draw relationship diagrams... if you're lucky there may already be diagrams created.

i know that SQL Server can do this, and i thought Oracle had a tool for this, but i could be wrong.

 

[kevinthenerd]

1. Make a pot of coffee.
2. Start poking around.
3. Ask your team members.
4. Get a little bit of sleep.
5. Wake up early.
6. See step 1.

I don't have an HT answer for you, but it's the most useful I have: I learned the hard way that it's easier to have good communications skills with your team members than to go poking through their files trying to figure out poorly documented code. Even if you look like an idiot, it'll be worth your trouble.

Edit: This is assuming that you can get in touch with the guy who made them.

 

[glugglug]

If there are foreign keys in place enforcing the relationships, TOAD can automatically generate an Erwin diagram of the table relationships. Usually they are not in place, however, because they slow down table changes and make some transactions more complicated (usually deletes).

I believe MS SQL Enterprise Manager can also automatically create a diagram for a set of tables.

Otherwise, you have to hope a column used as a key will have the same or at least a similar name across tables, and identity columns and/or unique constraints/indices are always a good clue which those are.

 

[glugglug]

Originally posted by: iotone
i know that SQL Server can do this, and i thought Oracle had a tool for this, but i could be wrong.

Oracle tools are abysmal. I assume you meant Qwest has a tool for this.

 

[velis]

You're approaching the problem from the wrong end. Typically you don't need to know all the tables on your first day. Take your first assignment, study it and then go ask relevant people about stuff you didn't understand from assignment documentation.
Care must be taken not to ask the same questions twice, to know what exactly you want to ask, etc.
Repeat this for n months to learn most of the relevant data and become one of those that new people come to ask. n (months) very much depends on your own interest in the project.