This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Add ALTER COLUMN options to modify numeric column length and allow rename column names for ((bi)temporal) column organized tables.
Db2’s capabilities to perform schema changes on any form of ((bi)temporal) column organized tables lacks behind it’s row organized counterparts. This prevents effective database schema evolution and therefore limits the use of column organized tables in our database environment.
We would need ALTER TABLE .. ALTER COLUMN options that allow at least
Modification of numeric column type lengths
Rename of columns
E.g. with growing amount of data we face the scenario that requires DBAs to increase DECIMAL type columns to allow for bigger numbers. Given current limitations with ALTER TABLE operations on column organized tables there is no way for us to apply common approaches that relational databases provide with row organized tables.
We are forced to consider approaches that involve unloading existing tables and re-load the data into new tables with the desired schema. This only works up to a certain amount of data given limited time during maintenance windows.
Adding functionality like temporal tables to this equation is limiting these kind of approaches even more as we need to ensure that data movement is not breaking the history nature of our data.
Adding these schema evolution options with ALTER TABLE for any form of column organized will boost usability in real life database scenarios a lot.
Do not place IBM confidential, company confidential, or personal information into any field.