Hi

I noticed that deleted space for blobs isn't being reused, is there a plan
to reuse deleted space?

--
Jan-Erik

Jan-Erik,

<< I noticed that deleted space for blobs isn't being reused, is there a
plan to reuse deleted space? >>

The space is reserved for the row that owns the BLOB.  When the BLOB for
that row grows again, it will re-use the space.  DBISAM re-used the space
globally, and it was a nightmare in terms of performance and concurrency.
You could get an #8708 error when opening a BLOB with DBISAM, whereas you
will not see such an error message with ElevateDB.

--
Tim Young
Elevate Software
www.elevatesoft.com

Dear Tim,

> << I noticed that deleted space for blobs isn't being reused, is there a
> plan to reuse deleted space? >>
>
> The space is reserved for the row that owns the BLOB.  When the BLOB for
> that row grows again, it will re-use the space.  DBISAM re-used the space
> globally, and it was a nightmare in terms of performance and concurrency.
> You could get an #8708 error when opening a BLOB with DBISAM, whereas you
> will not see such an error message with ElevateDB.

Can you add any kind of "Shrink" Database function as MSSQL ?

Thank you

--
Charalabos Michael - [Creation Power] - http://www.creationpower.gr

"Tim Young [Elevate Software]"  wrote
> Jan-Erik,
>
> << I noticed that deleted space for blobs isn't being reused, is there a
> plan to reuse deleted space? >>
>
> The space is reserved for the row that owns the BLOB.  When the BLOB for
> that row grows again, it will re-use the space.  DBISAM re-used the space
> globally, and it was a nightmare in terms of performance and concurrency.
> You could get an #8708 error when opening a BLOB with DBISAM, whereas you
> will not see such an error message with ElevateDB.

I do understand the problem. (when the blob is changed)
But, isn't it supposed to re-use the space when the row is deleted?

The thing that made this an issue (for me) was that I imported some records
(2-300MB of images) then deleted all the records and imported again and the
blob file doubled in size.
If I repeat (deleting/importing) it just keeps growing, alas the space is
not used again.

Unless this is a bug, a "Shrink" table command would be nice.

--
Jan-Erik

Charalabos


OPTIMIZE TABLE....

Roy Lambert

Michael,

<< Can you add any kind of "Shrink" Database function as MSSQL ? >>

As indicated by Roy, OPTIMIZE TABLE will do that.

--
Tim Young
Elevate Software
www.elevatesoft.com

Jan-Erik,

<< I do understand the problem. (when the blob is changed) But, isn't it
supposed to re-use the space when the row is deleted? >>

Yes, it should re-use the space when the row is used again.

<< The thing that made this an issue (for me) was that I imported some
records (2-300MB of images) then deleted all the records and imported again
and the blob file doubled in size. If I repeat (deleting/importing) it just
keeps growing, alas the space is not used again. >>

I'll have to check this out and see what I can find.

--
Tim Young
Elevate Software
www.elevatesoft.com

> << Can you add any kind of "Shrink" Database function as MSSQL ? >>
>
> As indicated by Roy, OPTIMIZE TABLE will do that.
>

Ok guys, Got it!

Tim, please add it into EDB Manager and also document about the full
features of OptimizeTable.

Thank you

--
Charalabos Michael - [Creation Power] - http://www.creationpower.gr

Michael,

<< Tim, please add it into EDB Manager and also document about the full
features of OptimizeTable. >>

It's already on the list from when you asked the last time.

--
Tim Young
Elevate Software
www.elevatesoft.com