Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Status Future consideration
Created by Guest
Created on Nov 2, 2021

Improve Config DB Performance

We have a Maximo database with approximately 5 million workorder records.

CONFIGDB is slow when adding multiple YORN fields to large tables.

In order to improve Config DB Performance the process should group the updates, rather than running individual updates.

For Example, replace this:

update workorder set field1 = 0 where field1 is null;

update workorder set field2 = 0 where field2 is null;

update workorder set field3 = 0 where field3 is null;

update workorder set field4 = 0 where field4 is null;

With this:

update workorder ( set field1 = 0, field2 = 0, field3 = 0, field4 = 0 )

where field1 is null

and field2 is null

and field3 is null

and field4 is null;


  • Guest
    Reply
    |
    Nov 3, 2021

    For SQL Server a default constraint is utilized so the database platform populates it on existing columns and then the constraint is dropped after. Oracle/DB2 syntax is different (you set a default on the column instead of a constraint) but I'd imagine the performance of that would be faster then executing a bulk update. Similarly after you would then need to drop the default.