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.
Need to support inplace reorg on partitioned table with global indexes
This is critical in a 2 sense; 1) Performance The customer has many range-partitioned table with global indexes and most of them left unreorganized because INPLACE REORG on Inplace reorg on range-partitioned table with a global index is not suppo...
https://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5.0/com.ibm.db2.luw.admin.perf.doc/doc/c0009677.htmlIn a pureScale environment, space that is freed up by a delete transaction on one member may not be reused by an insert transaction on a d...
In current design, when SQL statement accesses a table, the compression and expansion dictionaries of that table will be read into DBHEAP and kept there until database deactivation. For column-based table, the memory consumption may up to 100MB. i...
We would like functional/partial indexes, that is indexes that include a where clause. Currently when there is an index that includes a condition we have to put the condition as part of a field (NAME_IS_BLANK) and then include that conditional fi...
Use FSCR information to ommit empty data pages while performing Table Scan (TBSCAN)
ABSTRACT:Table scan over volatile table with large number of empty pages scans all empty pages instead of using FSCR to find pages to be scanned.VERSION INFORMATION:DB2 9.7.FP5 on Linux / DB2 9.7.FP9a on AIX 7.1 / DB2 10.5.FP4 on LinuxTECHNICAL IN...
Compression of Primary Key Indexes with Version 10.1 FP 5
While doing some testing with, we noticed that when you create a table compressed, that ALL indexes automatically get compressed. We found out that we have the ability to specify "normal" indexes without compression, but you can not have an uncom...
Support synchronous detachment of a table partition
Starting with DB2 9.7(?) the detachment of table partitions is handled asynchonously. To simulate synchronous behaviour a complicated work around has to be put in place. Such a behavior could be triggered by a new DML keyword such as ASYNC.
Currently it is merely possible to lock a complete table by means of the "lock table" statement. However, for range partitioned tables, it would be beneficial to be able to lock a specific data partition.That is, a statement like: â€œlock data par...
Do not place IBM confidential, company confidential, or personal information into any field.