Wählen Sie das Produkt, zu dem Sie Hilfe benötigen:
- Internet Explorer
- Media Player
- Windows Phone
- Weitere Produkte
Article ID: 92681 - View products that this article applies to.
This article was previously published under Q92681
This article has been archived. It is offered "as is" and will no longer be updated.
Novice: Requires knowledge of the user interface on single-user computers.
You can improve the performance of Microsoft Access if you periodically defragment your hard disk and compact your database.
Because the data on your hard disk becomes fragmented over time, you should run a disk-defragmentation utility (or defragmenter) periodically. If you often make changes to a database, portions of the database may also become fragmented. Therefore, you should run the Compact Database command in Microsoft Access periodically.
A disk defragmenter will place the database file in contiguous clusters on your hard disk, making file access faster. If you do not defragment your hard disk, the operating system may have to go to several physical locations on the disk to retrieve the database file, making file access slower.
Running the Compact Database command may also improve the performance of Microsoft Access. Compact Database makes a copy of the database file and, if it is fragmented, rearranges how the database file is stored on disk. The compacted database file is usually smaller than the original. Compacting can also speed up queries because it writes all the data in a table into contiguous pages on the hard disk. Scanning sequential pages is much faster than scanning fragmented pages.
You can use the original name for the compacted database file, or you can use a different name to create a separate file. If you use the same name and the database is compacted successfully, Microsoft Access automatically replaces the original file with the compacted version.
Limitations of Compacting
Defragment or Compact First?If you compact a database after running a defragmenter, you theoretically leave open disk space immediately after the .MDB file on the disk, allowing the operating system to place any additional information in the succeeding physical clusters. This would be very fast. However, if you defragment after running Compact Database, your .MDB may be placed on the first part of the disk followed by the rest of your files, with no open disk space until the end (the inside tracks) of the disk. This makes disk access somewhat slower.
For more information about compacting databases, type "compacting databases" in the Office Assistant, click Search, and then click to view "Compact a database to defragment the file and free disk space."
Article ID: 92681 - Last Review: October 14, 2013 - Revision: 2.1