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,
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.
Additional Information
To view our roadmaps: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io
Hi Ember,
(For some reason I don't see your reply in this Idea, although I received a copy of it in my notifications. )
I'm not that familar with the Python support for Db2 but the problem with the parameter markers might be because Python is trying to bind in a value, which is only necessary if the statement is actually executed, which shouldn't be the case when EXPLAIN MODE is RECOMMEND INDEXES. Does Python have support for preparing a statement or declaring a cursor? If so, that might avoid the issue. It works in CLP. i.e. "declare c1 cursor for select..." will result in index recommendations but the query is not executed until the cursor is opened.
Replacing the parameter marker with a literal could result in different index recommendations because the optimizer can compare the literal to the statistics to get a better filtering estimate. There are other optimizations possible such as introducing predicates implied via transitivity e.g. c1=1, c2=1 --> c1=c2.
Hi Ember,
Can you provide more details about why the RECOMMEND INDEXES and EVALUATE INDEXES explain modes are difficult to use from a Jupyter notebook and why using them would require the full Db2 client to be installed?
Supporting these explain modes with EXPLAIN_FROM_SECTION doesn't make sense architecturally because they require invoking the optimizer and that doesn't happen with EXPLAIN_FROM_SECTION. EXPLAIN_FROM_SECTION extracts explain information that is stored along with the access section and writes it to the explain tables. The SQL compiler and optimizer aren't called during this process. In order to support these index explain modes, the index recommendations would need to occur for every statement compilation and the resulting information would need to be stored along with the access section. This would increase prepare time and the size of access sections. I might be able to suggest an alternative way to accomplish what you want if I understand your use case better.