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,
Post an idea
Upvote ideas that matter most to you
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.
Looking to replace NPI with DPSI. DSPI is created, and would like to verify that all SQLs that were using NPI, when Rebound/executed dynamically would either
a) use either newly created DPSI or another index on the table
and b) have run time performance that is acceptable
Would like to verify before dropping the index.
Access Paths can be compared via tools, but real, run time performance is also needed.
Catalog Stats can be updated to fool DB2 into trying not to pick NPI, but they're not perfect.
If catalog Stats updated and a dynamic SQL statement has a poor path, it would need to be invalidated from the cache (ie via runstats) If the index is large, this can take some time.
Looking to be able to ALTER an INDEX to either have DB2 optimizer ignore this index at explain time, and then be able to ALTER back on, if needed. Static SQLs would need to be rebound, but dynamic SQLs using the table would be re-explained when the index is turned back on for optimization.
Do not place IBM confidential, company confidential, or personal information into any field.