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.
Currently on Db2 LUW CREATE OR REPLACE is only allowed for the owner of a database object. CREATE OR REPLACE authorization should be opened up to allow create/replace by anyone who has the ability to drop the object and to create the object with a...
need to provide a RENAME SCHEMA statement (other database products provide this)
Need RENAME SCHEMA other databases other than DB2 LUW (i.e. MaxDB from SAP) provide a statement RENAME SCHEMA to rename a schema like a RENAME TABLESPACE/TABLE/INDEX. Needed on all supported operating systems.
Full support for aggregate function with DISTINCT in OLAP SPECIFICATION
Use of DISTINCT with e.g. COUNT function in OLAP specification (PARTITION BY clause) returns error SQL0441N (SQLCODE -441).Due to the fact that Db2 does NOT support the use of DISTINCT option in such cases, we have a major impact with COGNOS gener...
DB2 optimizer in v10.5/v11.1 has still several weaknesses in generating correct plan when using RP tables, because it bases its plan only on global stats when partition (data and indexes) stats are available. Case TS001150102
Currently, in column-organized tables you cannot alter or rename columns and you even cannot drop columns. The only allowed operation is to add a column. This renders the column-based-tables pretty useless because in a normal environment, it must ...
Consideration of Statistical Views for INSERT with Sub-SELECT
We try to improve the performance on an INSERT with an underlying complex subselect eg. "INSERT INTO table "Therefore we created a statistical view through which the optimizer should be able to get more distribution statistics and build a better a...
SQLCODE SQL0302N should give hint which parameter is too long.
Scenario: prepared statementsError: host variable too longProblem: SQL0302N should give a hint which parameter is affected.Details:Using prepared statements with parameter markers such as INSERT INTO TESTTAB (COL1, COL2) VALUES (?, ?)"); DB2 throw...
Improve access plan resolution for SELECT MAX() (or MIN()) statements on range-partitioned tables with local (partitioned)
Context: range partitioned table with partitioned indexes A SELECT MAX() statement is issued on a field that is not the part of the partitioned key. The query is resolved by performing a full index scan on a partitioned index on that field. That...
It is common in the database world (DB2 but all the others I have worked with are the same) to have a separate product installed that generates code and submits it to the database for processing. Eventually, you will encounter SQL that doesn't pe...
Do not place IBM confidential, company confidential, or personal information into any field.