Hello Syafiq Hamid,
The delay you are seeing on your issuing CA is indeed consistent with heavy fragmentation in the AD CS Jet database. The supported way to address this is to perform an offline defragmentation using esentutl /d against the certsrv.mdb file, but it must be done with the CA service fully stopped to avoid corruption. The process is to stop the Active Directory Certificate Services service, take a verified backup of %systemroot%\System32\CertLog\certsrv.mdb and its log files, then run esentutl /d certsrv.mdb /s <system path> /l <log path> from an elevated prompt. This compacts and rebuilds the indexes, producing a new database file. Once complete, restart the CA service and validate issuance speed.
It is critical not to run esentutl /d while the CA is online, as that will break transaction consistency. Also ensure you have sufficient free disk space, since the defragmentation process creates a temporary copy of the database. After the operation, monitor the CA event logs and test issuance latency to confirm improvement. If you are in a clustered or highly available CA setup, schedule downtime carefully and replicate the procedure across all nodes. This is the Microsoft‑supported method to restore performance when Jet index fragmentation impacts AD CS.
If my answer is useful for you, please hit Accept the answer to support me.
Thank you,
HL.