Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on May 13, 2013

Provide more granular database-level privileges than just CONNECT, RESOURCE and DBA

We have a requirement to support a code deployment role where a user, whose job role is not a DBA, can release code into a given database.

The type of things they would be doing is:
* Creating and dropping procedures, synonyms, triggers, indices and constraints.
* Creating, dropping and altering tables.
* Updating data either directly or by calling stored procedures.

The requirement is that these users would create all these objects in the schema of the application owner and not their own schema.

Currently granting the DBA privilege in a database is the only way to achieve this.

However, the DBA privilege gives these users more access than we'd like. There are some tables we might not want them to select data from and we would not want them to run certain commands like 'alter fragment' or be able to grant privileges.

In Oracle they have created individual system privileges for all actions such as "select any table", "execute any procedure" and "create any synonym". The privileges CONNECT, RESOURCE and DBA are now roles made up of these individual privileges and maintain compatibility with the standards.

I don't expect that any Informix implementation should copy Oracle but I think more fine-grained privileges are needed in a world where there are more audits and compliance criteria than ever before (PCI-DSS and so on).