Focal Point
IBM iseries and Materialized Query Tables (MQT)

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/3501005872

March 31, 2008, 01:56 PM
<JuliaR>
IBM iseries and Materialized Query Tables (MQT)
We know how to create MQT'S (we think), we are having trouble knowing if they are working correctly or at all. There is so much literature out there, trying to find help to optimize our data warehouse we have built. During proof of concept, the IBIers had MQT's working, but contact has left the company to verify our db2 is still configured properly. Any help at all, will be appreciated.

Thanks,

Julia
April 01, 2008, 08:06 AM
LakVenkat
MQT works well. MQT is nothing but summarized tables. When you create MQT it creates ordinary tables. You should build indexes on to pof that for further performance gains.

In Addition to that, you have sql methods to rfresh the MQTs with options like mqtname.refresh from strsql.


Version 764 on iSeries, V5r4, Client running on Tomcat 5.xx
April 02, 2008, 08:24 AM
hammo1j
There's wf and db2 settings to switch MVs on. Use of the MV will depend on the query.

Try doing a query that is the equivalent of the view within the MV to guarantee you use the MV.

You should see the difference when the MV feature is switched off and on (should be able to do this in your .fex). If not you will have to go down the explain plan route to see if the MV is being used.

MV = Materialised View same as a MQT



Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2
Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo