My point Dag is that even though I did not checkpoint the database, Derby released the disk space back to the OS (Solaris 10) when I dropped the table, so my experience is not matching what Rick had mentioned in that the disk space would not be released until a checkpoint. My experience is saying that the disk space was released immediately.
Is there some implicit checkpoint being done? Note that my utility is connecting to the database using the network server mode and the database was not shutdown before the space was released back to the OS. -----Original Message----- From: Dag H. Wanvik [mailto:dag.wan...@oracle.com] Sent: Tuesday, March 29, 2011 10:32 AM To: derby-dev@db.apache.org Subject: Re: Question about TRUNCATE TABLE and freeing disk space "Bergquist, Brett" <bbergqu...@canoga.com> writes: immediately brought this down to 46Gb of disk space. I do not have a "checkpoint" in my utility application. You can call it from ij or via JDBC: "CALL SYSCS_UTIL.SYSCS_CHECKPOINT_DATABASE()" http://db.apache.org/derby/docs/10.7/ref/rrefcheckpointdbproc.html Dag
