• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 8.2. Dynamic Host Configuration ... > Maintaining the DHCP Database

Maintaining the DHCP Database

The DHCP database relies on the same Jet 4.0 database engine that is used by Microsoft Exchange Server. There is no ceiling on the number of client lease records that the database can hold. The DHCP database is largely self-maintaining, and it compacts itself periodically during idle time. It needs to be compacted because the size of the database is not actually dynamic. It grows as records get added, but does not shrink when they are removed. In addition to keeping the database size in check and eliminating unused space, compaction is also the standard way to resolve Jet-corruption errors.

Compacting the Database

Although the database compacts itself periodically, it never takes itself offline when compacting, so it does not do as efficient a job as it could. Thus, it is helpful to periodically take the DHCP server offline by stopping the DHCP service and manually compacting the database. Depending on the number of clients serviced by DHCP, the database should be compacted every one to four months. Servers that maintain more than a thousand clients should be compacted monthly, whereas servers that maintain a smaller client base can have their databases compacted less frequently.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint