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.
Ability to enable/disable query optimization for foreign keys at a statement level. Example, many ETL (Extract, Transform, Load) processes utilize SQL statements to verify data integrity when foreign keys are not enforced. In order to return correct results, the foreign key must be altered to disable query optimization prior the execution of the 'integrity checking' SQL and enabled afterward. Since the foreign key must be altered at the table level there is potential to inadvertently impact other queries that reference these tables during this time. This disabling/enabling process also requires ALTER authority on the child table and REFERENCE authority on the parent table. In other words, the entire process is extremely cumbersome and potentially dangerous. The ability to enable/disable at a statement level would streamline the process and protect other users from being impacted.
Do not place IBM confidential, company confidential, or personal information into any field.