Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     IBM iseries and Materialized Query Tables (MQT)

Read-Only Read-Only Topic
Go
Search
Notify
Tools
IBM iseries and Materialized Query Tables (MQT)
 Login/Join
 
<JuliaR>
posted
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
 
Report This Post
LakVenkat
Member
posted Hide Post
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
 
Posts: 7 | Registered: January 15, 2008Report This Post
hammo1j
Master
posted Hide Post
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
 
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     IBM iseries and Materialized Query Tables (MQT)

Copyright © 1996-2020 Information Builders