IBM Data and AI Ideas Portal for Customers

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

Post 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 product management 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 notification 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Feb 10, 2015

Parallel I/O work on indexes for SQL Inserts.(RIMS)

it would be wonderful to have parallel I/O work on indexes for SQL Inserts. For instance, a table with 6 indexes, A SQL insert is sent to DB2 from an app program,,, The Insert takes place on the data page, now the RID is known and can be used in parallel work on updating the index entries. Each index could have a parallel I/O task or split the work based on some sort of costing. Rather than each index being updated sequentially, as it is done today under version 7 at SF, the work is done in parallel, not having to wait on each index being updated before proceeding to the next index. A table with numerous indexes and a large index tree structure takes lots of sequential work to complete an insert. Parallel work would really Kick IT up a notch! Currently SELECT statements are capable of achieving parallel I/O and/or CPU. Inserts can benefit from similar parallel concepts & technology too. Please pass this on and let me know if there are questions.I see this as being a excellent way to increase SQL Insert performance on some of our newer Auto Pricing OLTP applications here at SF.