DHCP Server Performance Degradation: High CPU Utilization and Database Compaction (dhcp.mdb)

Lyn Lyn 40 Reputation points
2026-08-17T12:06:57.17+00:00

DHCP server database fragmentation 50000 active leases high CPU utilization lease allocation timeout EventID 1014 EventID 1016

DHCPServer service queue backlog JET database engine error 0x000005B4 dhcp.mdb lock contention jetpack.exe offline compaction requirement

central DHCP scope lease request latency packet drop rate 0x00000057 ESE database engine maintenance failure EventID 1053

Operating System Edition Windows Server 2022 Datacenter x64

OS Version 10.0.20348

OS Build 20348.2655

Hardware Platform Dell PowerEdge R750

Processor Intel Xeon Gold 6338 CPU 2.00GHz 32 Cores 64 Threads

Installed Physical RAM 128 GB ECC DDR4 3200MHz

Service Display Name DHCP Server

Service Principal Name DHCPSrv

Process Identifier PID 4188

Target Database File Path System32 dhcp dhcp.mdb

Target Temp Database Path System32 dhcp temp.mdb

Windows for business | Windows 365 Enterprise
0 comments No comments

1 answer

Sort by: Most helpful
  1. Allan Solomon Mejia 3,840 Reputation points
    2026-08-18T01:57:49.6433333+00:00

    Hello @Lyn Lyn

    Given the symptoms- high CPU, DHCP request backlog, JET errors, and dhcp.mdb contention, I'd investigate the DHCP database before assuming this is a CPU or hardware-capacity problem.

    For Windows Server 2022, Microsoft still supports Jetpack.exe for compacting the DHCP database. The key point is that this is an offline operation: you must stop the DHCP Server service before running it.

    I would schedule a maintenance window and first make a DHCP backup. Then:

    net stop dhcpserver
    cd %SystemRoot%\System32\dhcp
    jetpack.exe dhcp.mdb tmp.mdb
    net start dhcpserver
    

    Make sure tmp.mdb doesn't already exist. Jetpack creates a temporary database, copies the database records into it, removes the original database, and replaces it with the compacted copy.

    Before doing this, I'd also verify that you have a usable DHCP backup. Microsoft's DHCP APIs support backing up the server configuration, settings, and client lease database, which is particularly important before database maintenance.

    However, 50,000 active leases alone shouldn't automatically require manual compaction. If the problem returns shortly after compaction, I'd investigate the underlying cause rather than repeatedly running Jetpack. In particular, check disk latency/queue depth on the volume containing %SystemRoot%\System32\dhcp, antivirus/EDR exclusions, available disk space, DHCP audit logs, and the DHCP Server/System event logs around Events 1014, 1016 and 1053.

    Also check the configured database maintenance settings. Windows DHCP has configurable backup and cleanup intervals, and the DHCP database configuration exposes both BackupInterval and CleanupInterval.

    If this DHCP server is production-critical, I'd also consider implementing DHCP failover before performing extended database maintenance so clients aren't dependent on a single DHCP instance.

    I would not delete dhcp.mdb, JET logs, or manually replace database files while the DHCP service is running. If Jetpack itself returns a JET/database error, preserve the existing database and backup files and investigate database corruption before making further changes.

    Sharing these references with you:

    Microsoft Learn – Jetpack command

    Microsoft Learn – DHCP database backup AP

    Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.