Nope...

variable length data is stored in the overflow section of the table...

Downside of that is that when you read the row, it takes 2 I/Os. One for
the row space and one for the overflow.

If you were mostly writing less that 32k, I'd tell you to take a look at
the ALLOCATE clause. That does cause space to be reserved in the standard
table space. Which wastes space, but then the data only needs 1 I/O to be
read.

Charles


On Mon, Apr 15, 2024 at 2:20 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

Let’s say I have a table with a 5mb clob column.

Most of my transactions that write to the table mostly consist of 64k and
less chars written to the clob but we want to reserve the much higher
storage allocation for when we need it

When the 64k chars are written to that clob on the row, the entire 5mb of
storage is not written to disk is it??

Tia

Jay

Sent from my iPhone
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.