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 Optim
Created by Guest
Created on Oct 18, 2018

Estimate time for archive

This may only apply for Retirement since we use all reference tables without SQL. It would be a nice to have if Optim could have a function to take an archive request and attempt to estimate the time required to archive.  I see this as looking at items like:

1) the number of records in each table

2) the row size for the tables.  If the table has large objects - maybe using a sample size (allow input to sample size) to guess at the size of the objects - say maybe 100 or 1000 rows,

3) Get some of the data for each table and see how long it takes process records and write sample files.

We like to ensure that our archives complete within 12 hours.  I know that it will be a rough estimate but it should be better than what we can do. A report of the estimate time for each table would be good.  This would assist us to better know how to split an archive into multiple parts.

You could also include an option to maybe have Optim regenerate the AD to produce the AD and AR objects for the splits of the reference tables to fit within the desired time frame.