Andres, Until you study DB's a bit, it's hard to fully understand the 'why' of this....but if you take a 100GB DB, and delete everything out of it, it'll still be 100GB on the file system. The reason behind this is that the DB will never automatically 'shrink' the extra empty space out because there is a 'cost' associated with growing it, so it doesn't shrink it. As such, your DBA should be able to find out how much slack space exists in your DB, and restructure it appropriately to reclaim the space if necessary.
On Fri, Nov 1, 2013 at 9:32 AM, andres tamayo <[email protected]> wrote: > ** > Hi there > > i'm working in an activity which supposed to help me to release DB space. > i extracted some old attachments to a folder using an escalation with a > perform-action-save-atachement action and then directly through SQL delete > the records from B tables in this case was B2109 and B2109C1000000XXXX. > > After that i went with my DBA and ask to validate the database space but > for my surprise nothing has changed in term of DB space. > > i already try not to delete directly form database instead i put a set > $NULL$ on attach field on escalation after extraction but i get the same > results. > > any ideas how i can free som DB space deleting the attached document to > the old incidents. > > thanks. > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
