thank you a lot joining for this discussion, please note it's more about my own training than anything else
Rudy: I have read up somewhere that creating views are kind of precalculated since they're stored to be frequently used: "Materialized views are an Oracle Silver Bullet when pre-joining tables together for super-fast response time. " - found at dba-oracle.com.
I checked your book and found none of this but on the where clause performance tips, about indexing fk's and on & where condition fields.
I've been checking the create DDL statetement for several tables (automated by Oracle SQL Developer) and I found most tables do not have pk constraints, I think because most of them are collecting numerical data instead of representing entities (please correct me if I'm wrong). There aren't either indexes at all. I´ll dive into Oracle/SQL Documentation about indexing.
D: You mean dumping all the million-rows tables to a single one? what about all the different field names and disk space? The updates on the system are made from entire harddisks data although it may be every 3-4 months. I don't know if other university teams are inserting data regularly, but I'm sure they are not in the bunch of tables my fellows and I are dealing with.