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


Status Not under consideration
Workspace Db2
Created by Guest
Created on Aug 25, 2016

DB2 performance - Hash partition table

On the VLDB - Very Large Database environment.
DB2 should support hash partition table to improve performance especially pureScale environment.
  • Guest
    Apr 10, 2019

    The customer requirement of the following competitor's syntax for a "hash-partitioned" table:

    CREATE TABLE sales_hash
    (
      s_productid NUMBER,
      s_saledate DATE,
      s_custid NUMBER,
      s_totalprice NUMBER
    )
    PARTITION BY HASH(s_productid)
    (
      PARTITION p1 TABLESPACE tbs1,
      PARTITION p2 TABLESPACE tbs2,
      PARTITION p3 TABLESPACE tbs3,
      PARTITION p4 TABLESPACE tbs4
    );

    Can be emulated in Db2 using the following, which has been specifically optimized in Db2 11.1.3.3 (and later):

    CREATE TABLE sales_hash
    (
      s_productid BIGINT,
      s_saledate DATE,
      s_custid BIGINT,
      s_totalprice BIGINT,
      s_genpartkey SMALLINT NOT NULL IMPLICITLY HIDDEN GENERATED ALWAYS AS (MOD(HASH4(CHAR(s_productid)),4))
    )
    PARTITION BY RANGE(s_genpartkey)
    (
      PART p1 STARTING(-3) ENDING(-3) IN tbs4 INDEX IN tbs4,
      PART p2 STARTING(-2) ENDING(-2) IN tbs3 INDEX IN tbs3,
      PART p3 STARTING(-1) ENDING(-1) IN tbs2 INDEX IN tbs2,
      PART p4 STARTING(0)  ENDING(0)  IN tbs1 INDEX IN tbs1,
      PART p5 STARTING(1)  ENDING(1)  IN tbs2 INDEX IN tbs2,
      PART p6 STARTING(2)  ENDING(2)  IN tbs3 INDEX IN tbs3,
      PART p7 STARTING(3)  ENDING(3)  IN tbs4 INDEX IN tbs4
    );