IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Allow placement of tablespace BYTE and TEXT data in a separate dbspace from the table's base row data.

Allow specifying a normal dbspace for a BYTE or TEXT column to isolate IOs for the blob data from main row data for the table. This would be logged space just like IN TABLE as opposed to IN blobspace blob pages.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 2 2020
  • Under Review
Who would benefit from this IDEA? Any heavy use table with simple large objects that experience IO performance issues. Especially when the large object data is not always queried!
How should it work?

Perhaps the syntax might be:

colname BYTE IN TABLE USING dbspacename


colname BYTE IN TABLE( dbspacename )


colname BYTE IN TABLE FRAGMENT IN (dbspace1, dbspace2, dbspace3,...)

The FRAGMENT IN would only be ROUND ROBIN and the default if no dbspace is provided would continue to be the table's home dbspace(s).

With similar syntax for ALTER FRAGMENT ON BYTE/TEXT to allow for reorganization.

Idea Priority High
Priority Justification Reorganizing tables with logged simple large objects in table space is currently difficult and expensive. This would separate the reorganization of row data and large object data simplifying the operation.
Customer Name ASK Database Management - several clients
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions