IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • 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

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

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.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jan 3 2019
  • Will not implement
Idea Priority Low
Customer Name Ameriprise
  • Attach files
  • Admin
    Karthik Gopalakrishnan commented
    1 Apr, 2019 04:12pm

    All,

    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.


    Thanks,

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

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions