Freeing ispace after a delete.

The question I have deals with free space after deleting blobs from ispace. I have a 300,000MB database with probably 220,00MB in an ispace, in a single table. I need to perform and "update table" on the table but I know that I don't have more than 10MB free in the ispace. Since I know space will be at a premium. My plan was going to be 1 - create a new table (not a "TEMPORARY" table) 2 - copy n-rows from the original to "NEW" table 3 - delete the n-rows just copied 4 - loop on 2 and 3 until the entire table has been coppied 5 - drop the original table 6 - re-create the original table with the modifications 7 - repeat 2 -> 4 above until all of the data has been been copied. 8 - drop the table created in 1 above After reading the recent discussion about empty table extents not being returned to the "free pool" of disk space unless the entire table is unloaded, dropped, created, and loaded, I was wondering if the same thing happens with blob pages. I don't think so but I thought I ask the experts. Frank GE Medical Systems PS: You are probably asking WHY?? - well the database in on a removable disk, the disk can be placed into a system with a higher or lower database revision than on the removable disk, and the users expect to be able to read the disk. There is no DBA to do a conversion so the conversion must happen "transparrently" to the user with the exception of a dialogue box requesting a yes or no answer to the question "Convert Database ?" and maybe an estimate of the time the conversion will take.