IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Database extensions should have a provision to create indexes only on ACTIVE tables.

Database extensions should have a provision to create indexes only on ACTIVE tables. As most of the queries/monitoring and reporting are performed on the ACTIVE tables.

These indices may not be always needed on the HISTORY tables.

  • Guest
  • Mar 18 2021
  • Future consideration
What is your industry? Non-Industry Specific
How will this idea be used?

This way Database resource utilization can be optimized.

And Index addition configuration can be done selectively with for ACTIVE alone or for both ACTIVE & HISTORY.


  • Admin
    Aaron Cutter commented
    3 May 03:42pm

    Thank you for your feedback Sunith. One concern with this approach would be the potential unexpected performance degradation if a user did end up making a query on both the active and history tables (i.e. ReadFromHistory="B" for order search) without realizing that the history table did not have the index. This would of course be a smaller risk for less commonly searched history tables, as you have suggested. Since we have not heard this request from other sources, we will give it some time on the Idea portal to see if others up-vote it and can consider it for a future release if appropriate.

  • Guest commented
    3 May 08:15am

    Hello Aaron,

    Most of the time we will need a wider search strategy mainly on Active tables. Such a wider searching would not be really needed for History tables. As there would not be a lot of queries, And usual volume between HISTORY to ACTIVE tables are in 3:1 ratio. Indexing space is also similar without using much of HISTORY indices.

    It would be nice to have more flexibility to the implementer by selectively creating indices either on active and/or history tables.



  • Admin
    Aaron Cutter commented
    1 Apr 07:31pm

    Hi Sunith, thank you for your Idea submission. To help me understand the request better, is there a specific scenario where having the index on the history table is leading to a big impact?

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.