Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Jan 29, 2026

Enable "MAINTAINED BY SYSTEM" in creating an MQT

Complex  SQL views are slow so when response time is paramont I firstly create an MQT by executing a

 CREATE OR REPLACE TABLE (table name)

 (some SQL) 

DATA INITIALLY IMMEDIATE

REFRESH DEFERRED

MAINTAINED BY USER

 

and then query this table.

 

However, I alway need to explicitly create this MQT prior to using it

If the option MAINTAINED BY SYSTEM was availabe then we will have 

an SQL view with a LF-like respone time. 

Idea priority Medium
  • Guest
    Jan 29, 2026

    Agree with the Guest comment.

    However, the system should be maintaining MQT automatically. Each time it is needed, the process should not have to stop to Refresh table. That should be a no-brainer. Do we rebuild keys in Indexes or LFs everytime we access them? No.

    This is an excellent idea in my opinion.

  • Guest
    Jan 29, 2026

    An MQT is designed to be a snapshot of the data on a certain moment. You don't have to recreate it, just REFRESH TABLE to refresh the data in the MQT