Oracle's answer to this dilemma is the materialized view. Database designers can use materialized views to prejoin tables, presort solution sets, and presummarize complex data warehouse information.

I'm not much of a DB guy, I just read stuff out of them. For an application we have, some data is coming from views (specifically made for the application) that join up tables from various sources ...