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 Under review
Workspace Informix
Components Informix Server
Created by Guest
Created on Jun 22, 2022

Identify/log slow queries on a busy system

SQLTrace offers the DBA the tooling required to monitor a user session. However its difficult to monitor heavily used systems. For example one needs to have a buffer large enough to store 90 seconds of SQL queries (small lookup SQL's consume the buffer really quickly) and copy syssqltrace every minute or less to a static table, filtering queries whose execution time is above a specific threshold.

This approach is wasteful and is prone to have gaps on the data depending on system load. For this purpose, I am proposing to implement a query log similar to the "slow query log" in MariaDB/MySQL ( and PostgreSQL (

This RFE is about, implementing slow query log as follows:

* Introduce a parameter equivalent to MySQL/MariaDB long_query_time or PostGreSQL log_min_duration_statement

* Write to a table/file the query whose execution time exceeds the parameter introduced above. At this stage the query plan is not required as the DBA can generate it at a later stage. Given that the engine, has all the information at hand, the writing out this information is cheap in terms of computation resource, yet extremely valuable for the DBA.

Needed By Month