Why it is Essential to Regularly Compact and Repair Microsoft Access Databases?

One of the most powerful features of Microsoft Access is that it allows databases to consistently increase in size. This way you do not have to worry about size limitations while developing the databases or while working on them. On the other hand, this means that even if you delete a record or even entire tables, Access simply indicates that the space may be made use of, for new records without actually giving up the space. Similarly, even if any extra space is created when you shorten or possibly modify records, that space is not released. This will not only cause enormous amount of defragmentation of the database, but more importantly it will eventually lead to corruption in the MDB files. The only way to restore data from the damaged files may then be to resort to high level MDB recovery.

The best way to make use of the extra space and the space created by deletions is to regularly compact the Access database. On the other hand, not compacting the Access database at all will mean that the extra space is being wasted and the database will continue to demand more space as more records are added.

Fortunately, Microsoft Access provides a powerful Compact and Repair tool that can be used to make use of the space available and to prevent excess defragmentation of the database. This tool works in two phases – in the first, it compacts the database so as to get rid of all the extra space and in the second, it repairs the MDB file if the fragmentation had caused any damage to it. The tool also helps in reducing the physical size of the database thereby making it more manageable for Access and also reducing the risk of requiring an extensive MDB recovery process. In fact, compacting an Access database is the only way that you can actually reduce the size of the database.

The frequency with which you should run the Compact and Repair tool depends a great deal on how often you use your Access database and more importantly on how frequently you add, modify or delete records from the database. If you are a regular user, then it is important that you run the tool often to reduce the risk of corruption in the MDB files. If you do not compact your database regularly, chances are that the MDB file may become corrupted at some point in time. You can then use the Repair utility to actually repair the corrupted MDB file. However, you should bear in mind that this Repair utility can only restore corrupted data objects such as records, tables and indexes.

If after running both the Compact and Repair tools, your database still appears damaged, there is no need to panic. It should still be possible for you to restore almost all your data but you will need to use more specialized, third-party tools such as Advanced Access Repair from DataNumen to carry out an MDB recovery. While these tools are very powerful and have the ability to restore data from seriously corrupt MDB files, they are also very efficient and easy to use.

The official website of Advanced Access Repair is http://www.repair-access.com/.

Article Source: http://EzineArticles.com/?expert=Alan_Nice

This article explains why and what the ‘Compact and Repair’ feature is when using Microsoft Access databases (version 2003 or earlier) though it also applies to later versions (Access 2007 and 2010 uing the newer file extension .ACCDB).

The author is spot on regarding why you use it and how it basically works which is very clear. I like to refer to ‘Compacting’ the database which reduces the file size issue (as a fragmented file) by ‘squeezing the air out in between‘ bringing the file into a normal manageable size.

The added point to mention here is the ‘Repair’ element which also releases the locking file (.LDB file) when used in a multi-user environment and therefore adminstrators should ensure they are the only user using the database (as exclusive mode) before running this utility.

Here’s a brief history of Microsoft Access

Here’s a brief history of Microsoft Access just in case you wish to step back and reminisce

A brief history of Microsoft Access

Late 1992, Microsoft released the first version of Access (version 1.0) desktop database application for the Windows operating system and was shortly replaced with version 1.1 in mid 1993 to incorporate better compatibility with other Microsoft Office products of that time and more importantly introduce the ability for programmers to code this application using Access BASIC.

Version 1.1 was buggy! and had performance issues and in the same year Microsoft released Windows 3.1 operating system along with Microsoft Office 4.3 Pro (suite of applications including Excel, Word, PowerPoint with Access – version 2.0) as it required the improved hardware, software memory and the power supported by Windows 3.1.

This was an ideal desktop database application tailored to the small to medium sized business that required a low cost database. At that time, the capacity of a disk hardrive was less than 100 MB (mega bytes) and typical document file sizes were in the 100’s of bytes. Continue reading “Here’s a brief history of Microsoft Access”