unstructured data. These data will to a large extent (but perhaps not
completely) be replaced by structured data (in some user defined data type) in
another column. This will reduce the space requirements considerably for each
particular row.
Hi Karl, thanks for the follow-up.
As Myrna suggeste
I wonder if you realize the only way Derby (and other darabase systems) gives
space back to the OS is when it's freed up a page. Typically data is not
restructured to that extent on an update. So if a page initially had 3 rows
because each row had lots of data in one column, after update, the pa
Hi Bryan,
thank you for your answer. My problem is the following: You may think about a
table with a column (among others) that contains a large amount of
unstructured data. These data will to a large extent (but perhaps not
completely) be replaced by structured data (in some user defined data
I want to make the unused space availabe to derby for the insertion of new
rows. It should be optinal to give unused space back to the OS. In order to do
so, I have to use some system utility.
I'm not totally sure whether the 5th word in the above line is "optional"
or "optimal".
To return unus
