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.
DB2 currently committed semantics available in a pureScale environment
[Background]Customer chose DB2 pureScale as their enterprise-level integrated database and is building four members and two CFs as their pureScale environment. The important keys DB2 pureScale chosen by customer are : - flexible application workl...
Possibility to index only specific rows of one or more columns. This could be implemented with a WHERE clause in the index create statement and would rsult in a tiny index for exactly the rows you are interested in.
Remove per-tablespace size limitation for v11.1 and v11.5 community edition
Currently if we restore a database backup that was taken on a higher edition of Db2 into Developer-C, it fails with SQL1139N, even if it is fully less than 100GB. There are two workarounds for this:
Set a MAX for all table spaces before taking ...
æˆ‘ä»¬å¸Œæœ›ç»™ç´¢å¼•æ·»åŠ ä¸€ä¸ªå±žæ€§visible on/offæ¯”å¦‚ï¼šALTER INDEX VISIBLE ON ï¼ˆé»˜è®¤å±žæ€§ï¼‰ALTER INDEX VISIBLE OFF ï¼ˆç´¢å¼•ä¸å¯è§ï¼‰å½“ç´¢å¼•ä¸å¯è§ä»¥åŽä¼˜åŒ–å™¨æ— æ³•ä½¿ç”¨ä¸å¯è§çš„ç´¢å¼•ï¼Œå¦‚æžœéœ€è¦ï¼Œç›´æŽ¥alter index...
The reorg online process need to lock the table in order to conclude. This is not a problem when you dont have many transactions, but when you have a 24x7 intense workload you might have a huge impact on your application.
Increase the maximum size of a LOB object per table or per table partition
SQL and XML limitshttps://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.sql.ref.doc/doc/r0001029.html
The maximum size of a LOB object of 4 terrabyte leads to the necessity of partitioning the table just due to this limit. Sin...
In current design, when SQL statement accesses a table, the compression and expansion dictionaries of that table will be read into DBHEAP and kept there until database deactivation. For column-based table, the memory consumption may up to 100MB. i...
Recommend/evaluate indexes – more information for each index
This is a point for tuning with indexes -> Tuning with indexes is still very common and useful.While using recommend and evaluate indexes it is possible to investigate each recommended index by updating USE_INDEX column in the table ADVISE_INDE...
Remove The Need To REORG A Table Up On Performing Table Alter/REORG Recommended Operations
Today when we perform certain operations aka REORG recommended operations against a table like adding columns, dropping columns, changing datatype of a column, altering NULLABILITY of a column etc. the table will be put in a state called REORG pen...
Do not place IBM confidential, company confidential, or personal information into any field.