This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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 updateson them if they matter to you. If you can't find what you are looking for,
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.