Results 1 to 3 of 3
  1. #1
    Join Date
    May 2003
    Provided Answers: 5

    Unanswered: Database Bloat on Networked Backend

    I have a backend data base whose size when compacted stays at about 127mb

    Just recently the backend has begun to bloat - I do not mean 5 or 10 mb from running import/export utils - I mean jumping from 127 mb to 497mb then 1 gb!

    I re-compact and it will stay at 127 - 135mb for a few days or at the leat a day then all of a sudden it jumps up to 3 to 4 times its size.

    any ideas?
    Dale Houston, TX

  2. #2
    Join Date
    Mar 2009
    Provided Answers: 15
    First thing I would try would be:
    1. Create a new database.
    2. Import every object from the existing one except system (MSys...) and temporary (~...) objects.
    3. Compile and compact the new one.
    Have a nice day!

  3. #3
    Join Date
    Nov 2004
    out on a limb
    Provided Answers: 59
    reasons for bloat?
    lots of rows being added, deleted or changes made to memo columns
    changes to the design of queries or something else being written back
    using temporary tables in the backend... a daft idea but Ive seen it happen before. if y'need temporary tables stuff 'em into your individual users front end, but try not to crearte a new table each time, but reuse the existing structure
    but 127...>497-->1Gb in a few days suggests there is somethign seriously out of wahtck

    Sinndho's suggestion is a good starting point, there may be soem form of corruption in the backend
    starting form a clean new db and importing the objects may fix trhat
    I'd rather be riding on the Tiger 800 or the Norton

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts