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.
Pain point: Index rebuild stops if user terminates the connection accessing the table with an index that is marked inconsistent and it starts over from the beginning again on next table access by another user. Scenario:An index object is marked in...
DB2 should allow offloaded backup of SMS tablespace to Tivoli FlashCopy Manager
I have an AVP customer who has a 3TB database upgraded from DB2 v8.x. Most user data tables are in SMS tablespaces. They wish to use Tivoli FlashCopy Manager to take database backup and reduce the time for database restore. However, for SMS tables...
Allow converting of the SYSCATSPACE to the reclaimable storage.
There is no way to convert the Catalog tablespace to RECLAIMABLE storage. The only workaround is to create a new database and to migrate the objects and the data. Since, we have a lot of databases which were created in pre-9.7 versions, we are stu...
UNIQUE INDEXES over BIGINT column can't be compressed
unique indexes over id columns (bigint) are not compressed whereas the same unique index over decimal column gets compressedindex compression for unique indexes is urgently needed to reduce disk and memory footprint
To remove tablespace maintenance restrictions on pureScale
To remove all the restrictions of SQL1419N Reason code = "11" on pureScale. 11 Altering database containers is not supported in a DB2 pureScale environment. As a result, the following clauses are not supported with the ALTER TABLESPACE statement i...
Possibility to index only specific rows of one or more columns. This could be implemented with a WHERE clause in the index create statement and would rsult in a tiny index for exactly the rows you are interested in.
Do not place IBM confidential, company confidential, or personal information into any field.