Skip to Main Content
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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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:

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:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Jun 22, 2016

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 uncompressed Primary Key. We noticed some degradation on loading the table with indexes and Primary Keys compressed.

As a work around, we dropped and recreated all indexes without compression, then created a Unique Index and tied it to a primary key constraint.

We were wondering if IBM would consider an enhancement of allowing primary key uncompressed.
  • Guest
    Apr 1, 2019


    As per discussion with Development (Matt Emmerton), we decided to reject this Idea/RFE due to following reason. If you would like re-open or get more details on this Idea, please reply as public comment. 

    Reason for rejecting this Idea/RFE:

    There are many properties of indexes that are allowed in a CREATE INDEX statement that are not allowed as part of a CREATE TABLE ... PRIMARY KEY or ALTER TABLE ADD PRIMARY KEY statement.
    In these situations, the CREATE TABLE ... PRIMARY KEY statement must be decomposed into separate CREATE TABLE, CREATE INDEX and ALTER TABLE operations.
    This is the solution that you have devised to support the combination of a compressed table with an uncompressed primary key index.

    While we agree that it would be beneficial to achieve this effect via a single CREATE TABLE ... PRIMARY KEY statement, it would require extensions to the SQL language syntax which we believe are inappropriate and are unlikely to succeed.


    Karthik Gopalakrishnan
    Advisory Offering Manager, IBM Db2
    Mobile: +1 469 996 6850