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,
Post an idea
Upvote ideas that matter most to you
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
This will be very good feature to add as in some environments table can be huge like I had in one of the projects . 1 table was more than 1 tb of size and we never did reorg on that. Just runstats with sampling option. So if we have reorg on fragmented area then it will be good for performance.
Very much needed feature. I can relate it to an issue we have at present where we are not getting downtime from customer as the table is huge and is pending for very long time resulting in performance issues. It wil be very beneficial for both, us and the customer.
Good idea
There are customer who does not use online reorg because it takes a long time for huge table, reducing time will help them to save down time for offline reorg. Good idea!
Good idea!! The customer will save lot of down time for the Offline Reorg , if this idea gets implemented in Inplace Reorg and also the execution time improves. It will say save lot of time and cost for the customers!
To me this seems a key improvement feature for DB2 which makes the DB2 experience for our clients more valuable.
Let me add, this idea would be very beneficial to many customers. TIme and resource saving are critical and this feature would appeal to many customers.
I like this idea
It a good alternative to minimaze downtime for customers in a days downtime is becoming more and more unacceptable and high availability is crucial for clients
As this procedure is critical to keep the database performance and healthy , reduce this time will help customers to not have a huge maintenance window to execute the procedure and keep the environment up and running in its best way.
I like the idea , I remember when I was working with Commerce on Cloud, we used a tool called db2collect. Have you heard? So through db2 collect I understood what tables should run reorg. The procedure was very critical, imagine a Transactional table for an e-commerce site. The maintenance window was not large. So this idea matches a lot the requirements related to an e-commerce workload.
This feature could be beneficial, especially if you can reorg within a data partition
It will a good feature to add.
Good Idea it's really useful.
It is a great idea!
It is a great idea, we have faced a lot of times with the extra fs problem from OS point of view, it is required an extra prepare task for example requests of extra disks for the LUN if there is no free capacity in the vg, another benefit, if we are in the special case and we have to perform online reorg during daytime, this solution help to us to reduce the time of the performance related problems during the reorg is running when the customer is using the database.
The idea of only doing a reorg of "sparse" pages or pages with a large % of overflow records as an added option to inplace reorg seems like a good idea and could potentially reap a large time savings compared to a full scan reorg while still providing needed I/O efficiency to SQLs that scan large numbers of pages.
Its a Nice idea.
Awesome Idea.
It is really a Great Idea, many customers, like SCOR, has rised their interest in a such feature.