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.
Support synchronous detachment of a table partition
Starting with DB2 9.7(?) the detachment of table partitions is handled asynchonously. To simulate synchronous behaviour a complicated work around has to be put in place. Such a behavior could be triggered by a new DML keyword such as ASYNC.
System Tables should come with STATISTIC PROFILE set from factory
We all know how important STATISTICS are, and more specially, how they are captured for each particular table ! Documentation says that DBA and application sholuld determine best options, based on usage.. but ibm is lacking to do the same fo...
SAP BW needs to materialize data into persistent (regular) tables to be able to access it from multiple session (connections). CGTT and DGTT in Db2 cannot be accessed from multiple sessions/connections. Therefore those temp tables that don't requi...
To remove tablespace maintenance restrictions on pureScale
To remove all the restrictions of SQL1419N Reason code = "11" on pureScale.11 Altering database containers is not supported in a DB2 pureScale environment. As a result, the following clauses are not supported with the ...
Increase the number of ALTER TABLE operations that can be performed online without placing the table in "reorg pending" state
There are a few operations that seem to place the table into "reorg pending" state immediately when it should be possible to treat them as REORG-recommended.For example, any ALTER COLUMN .. DROP COLUMN statement that doesn't affect indexes should ...
The option ordinality is used in XML queries but the overall performance is very slow
We use the for ordinality option in our queries but the over all performance is very poor.There is a specific XSCAN needed when ordinality is specified which takes a long time.this XSCAN produces a sequence of XML ELEMENTS. This sequence is then f...
https://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5.0/com.ibm.db2.luw.admin.perf.doc/doc/c0009677.htmlIn a pureScale environment, space that is freed up by a delete transaction on one member may not be reused by an insert transaction on a d...
Do not place IBM confidential, company confidential, or personal information into any field.