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

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 (

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 updates on 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Not under consideration
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