Results 1 to 4 of 4
  1. #1
    Join Date
    Nov 2006
    Posts
    1

    Question Unanswered: 2GB Access DB Issue

    The company that I am working for has an "issue tracking" web based software called, FogBugz, it uses MS Access DB as its back end. The issue that we have now is the DB is 2GB in size and does not accept data to be added to it anymore. Is there a way we can compress it or split it so we can at least keep working until we can migrate to SQL?

    I have tried the MS Access built in spliter but it didnt work, it just created another 2GB copy of that database.

    Any help will be much appreciated!

    Thanks!

  2. #2
    Join Date
    Apr 2005
    Location
    Zagreb - Croatia
    Posts
    372
    Did you try to COMPACT your MDB.

  3. #3
    Join Date
    Jun 2005
    Location
    Richmond, Virginia USA
    Posts
    2,763
    Provided Answers: 19
    In an app this large, you've probably deleted scads of objects of all types, many of which may still be counted against the 2 GB limit. It will no doubt be a PITA, but you might consider the old "create a blank DB and import all objects into it!" I would do this in conjunction with MStef-ZG's idea. This may buy you some time, at least, until you can migrate to something else, such as SQL where you can, hopefully, still use your Access frontend.

    Good Luck!
    Hope this helps!

    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

  4. #4
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    Provided Answers: 59
    agree you will probably get some space back using a compact and repair on the data. However a permanent fix may be to either cull the data... delete duplicates or aged / obsolescent records

    OR
    shift to a different backend.

    OR
    the other thing you could consider doing is seeing if the datatypes are reasonable. the system designer may have specified say 20 characters for a column that you only use 10 characters for.... reducing that over many hundreds of thousands of rows will be significant. also consider settign text datacolumns that you dont use to 1 character. if you do tinker with the data defintions remember to back up the data first, and compact & repair the db afterwards. I'd also reccomned dusting down the CV just in case it goes wrong

    HTH
    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
  •