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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Not under consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on Jun 3, 2014

SQL skeleton for SQLTrace

SQL skelecton for SQLTrace

Most of the customers' product system have to run almost 1000 transactions per seconds, it means there are about 86M transactions per day. so there will be to many SQLs would be traced by current SQL trace.
so customer cannot turn on SQL trace in their product system to cache the SQLs history data for 1 week,1 month.

In most of the customers' system, there are only less than 1,000 different SQLs. Each SQL run with different filters, such as,
select * from tab where c1=1;
select * from tab where c1=2;
...
select * from tab where c1=1000000;

it should be traced as 1 single SQL in the SQL Tracing.
select * from tab where c1=?

it does not to store all the execution information for the 1000000 SQLs, we just need to store 1 SQL information, calculate the max and avg execution time, and count the total execution times. And only store the detail information, if it execute for a very long time (set a threshold, as > avg * 200%) or using full table scan way.

so in this way the sql trace information is very small, and it very helpful for DBA to find problems.