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.
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...
More and more SQL is stored in repositories and needs to be applied in odd places and orders. One syntax element that supports this is the "IF EXISTS" on a drop statement. This causes a statement to not count as a failure if it finds no object to ...
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...
Add ability to detect changes in data (similar to QSYS2.DISPLAY_JOURNAL)
When supporting a production environment, one needs to detect the sequence of updates, including before and after image.On IBMi, we use extensively the functionality to consult the journal entries (https://www.ibm.com/support/pages/qsys2displayjou...
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
Enabling readonly mode for database or user. (DB2 LUW)
Would like to see a db level and a user level parameter to enable readonly mode at database level or user level. Currently need to run set of statements to achieve this, which makes management difficult. A single statement to enable readonly mode...
Functions for converting Unix Epoch Time and Dealing with RHEL 8 Native Posix MQ
SQL scalar functions for Converting between human-readable date/time and Unix Epoch Time. For example:db2 "values ept2date(123456789,0)" is equivalent to Linux GNU date commanddate -d "1970-01-01 1234567890 sec UTCdb2 "values "date2ept('now')"is e...
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 ...
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.
Do not place IBM confidential, company confidential, or personal information into any field.