reverse engineer 500 table oracle database: by sections?

[rlo0323]

folks,

i am reverse engineering a 500 table oracle db. i selected the whole
encilada: pk/fk, triggers, views, stored procedures, etc etc.
i will not integrate shapes on the reverse engineering process. (why? no
clue! but a message box popped up and said this was not a good idea! so, ok,
won't do it!)
i tried the whole enchilada, but with just 10 tables, and filled a page. if
i had done the 500 taqbles, i can't imagine what it would have looked like.
since this MUST be expanded for viewing on multiple pages, i wonder how to
do that?
do i need to do the reverse engineering by some kind of sectioning? 100
tables at a time (for example)?

i don't have a strategy for the reverse engineering, and this is my first
time at it. and i don't know/understand the impact of integrating shapes, so
i thought i'd ask for input.

interesting though: on the 10 table first test of reverse engineering the
'whole enchilada', i found a 'fatal error' on a backup set of indexes -- this
was greeted with sheer delight by the dba group. since i am in the user
community, you can imagine the red flags that went up. nice tool, this visio
2003, hi-impact.

i sure could use some practical feedback on a reverse engineering 'process'
or some kind of 10-step 'cookbook'.

thanks, ron

 

[Al Edlund]

you might start over here..

http://msdn2.microsoft.com/en-us/library/aa140264(office.10).aspx

al