> Here’s a list of things that can go wrong (here in the context of domain controllers) That article was written because DC is a business-critical infrastructu

> Here’s a list of things that can go wrong (here in the context of domain controllers) That article was written because DC is a business-critical infrastructure. Here’s a comparable one about Oracle: https://docs.oracle.com/cd/A87860_01/doc/server.817/a76965/c28recov.htm https://docs.oracle.com/cd/A87860_01/doc/server.817/a76965/c... NTFS: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831536(v%3dws.11) https://docs.microsoft.com/en-us/previous-versions/windows/i... > Not quite reasonable for a database containing a search index on a consumer device. Before I switched to MS Outlook, I was using Windows live mail (now discontinued) as an e-mail client for a decade or so, it used ESENT for everything. When I run process explorer and search for “esent.dll”, it finds a dozen of system services using ESENT databases, many of them critical like CryptSvc. I try to buy good hardware, but that’s not server-grade components. I don’t use ECC RAM nor a UPS, and I suffer from brief power outages couple times a year. If ESENT would be corrupting databases when the power is turned off suddenly, I would have noticed.