During the refresh of an MQT (either INCREMENTAL and FULL refresh), there is
a time associated to join the dimensions and fact tables involved on the MQT.
Depending on how well tuned your physical data model is, it provides significant
results during population of MQTs. Also, there are different techniques that you
can take to populate the MQTs like load instead of refresh, or avoid logging data.
During query execution time, the DB2 optimizer considers the MQT like regular
tables when it comes to access plan strategies. Good indexes on MQTs also are
important for query optimization as well update statistics on base ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month, and much more.