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.
View invalid but be able to check if the dependant object(RIMS)
If an object that a view is dependant on (table, UDF etc) is dropped Rather than becoming permanently inoperable the view should become invalid but be able to check if the dependant object has been restored the next time it is accessed. If the dep...
Ability to limit tablespace objects to specified schema-qualified names(RIMS)
As described in the 'transportable tablespaces' requirement, customer uses ï¿½ a 1:1 mapping between a schema and it's tablespaces. ï¿½ They want an option that will allow them to enforce this 1:1 mapping. For example, only objects with schema mys...
Enforce index name uniqueness at table level; not at schema level(RIMS)
currently all index names for a partiuclar schema must be unique. This is painful when there are tens of thousands of indexes. They want to be able to use duplicate schema names as long as the name is unique per table that the index is defined on.
wait-for-delay functionality (server side sleep without spinning CPU)(RIMS)
Customer requests the ability to add a server-side sleep function that does not consume CPU or require an external routine. Such a routine would be useful in that it can be added to an SQL procedure to perform a sleep/delay, without having to intr...
A REBALANCE utility that rebalances container maps (rather then filling in gaps)(RIMS)
The current REBALANCE utility actually moves extents around from higher stripes to lower stripes to fill in gaps of empty extents. This means that containers are not necessarily 'balanced' (ie. contain the same number of extents) at the end of the...
way to make 'COMPRESS YES' the default for all CREATE TABLE/INDEX statements.(RIMS)
Customer would like a means to be able to make 'COMPRESS YES' the default behaviour for CREATE TABLE and CREATE INDEX statements. Since the customer's enterprise-data-warehouse database is used by many vendor applications, it's onerous to modify v...
Do not place IBM confidential, company confidential, or personal information into any field.