Deleting Archived Workflows does not decrease database size

Jaleel_Shaheen_(alico01admin_-_(deleted))

We have been using workflows extensively and had more than 30000 workflows on the system of which half were archived. The database size of our instance was 6.14GB and we thought workflows to be the reason for this unwanted load on our database. Hence we planned to delete the archived workflows. We got some help and lot of warnings to not to touch the Livelink Schema directly and use LAPI instead. We developed a LAPI application that would delete all the archived workflows and hoped that it will also delete all the sub workflows and any attatchments they might have. Anyways after taking all the necessary backups we executed the program which deleted all the archived workflows, but to our surprise the database size has decreased only in fractions and stands at 6.04GB.In some of the workflow tables the number of rows have decreased by half but in others the data size has grown dramatically e.g., WMapTask 500MB -> 1700MBIs there something that we missed in the process? We did use code similar to the one mentioned in the discussion above and the archived workflows are no more on the system but the database size is still massive. We are not using any other features of Livelink in our production at the moment i.e., documents, discussions, news, projects, etc.Any help/comments would be appreciated.Thanks & RegardsJaleel Shaheen