When -all- records from a table with a varbinary(max) columnÃÂ are deleted (not via truncate), the table properties
still show a dataspaceÃÂ size from before the delete operation.
Inserting new blob records only leads in the growth of the allocated space withouth reusing the empty
already allocated space.
Runnning commands like dbcc updatusage/checkdb/cleantable/reindex or sp_spaceused @updateusage = N'TRUE'
seem to have no effect.
Does anyone know when space allocated by a varbinary col. is released?
running SQL 2005 STD ed SP2. DB is in simple recovery mode.
View Complete Post