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.
|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( 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).
|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|
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 "firstname.lastname@example.org" 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