The setup we still walk into.
We have been saying this since 2022, and it's only become more urgent: there are still plenty of dental office servers running on a single partitioned spinning hard disk, or on two separate mechanical drives, one for the OS and one for data, with no RAID and no redundancy.
Both setups have the same fatal flaw. When a drive dies, and mechanical drives do die, the practice stops. No practice management, no imaging, no schedule, until the server is rebuilt from backup. That's hours to days of a closed practice riding on one component.
One disk can't do two jobs anymore.
A dental server is doing two heavy things at once. It runs the operating system, and it serves the practice management database and imaging storage to every operatory at the same time. On a single mechanical disk, those two workloads fight over the same read/write head, and everything slows to the speed of that one drive.
It does not matter how many parallel transactions the CPU can process. If the storage is a spinning disk, the disk is the bottleneck, and no amount of processor headroom fixes it. Solid state storage removes the seek-time bottleneck entirely, which is exactly why it's no longer optional on a server this busy.
This is the part people miss. Buying a server with a fast CPU and plenty of RAM, then putting it on a single spinning disk, is like putting a race engine on bicycle tires. The storage decides the real-world speed.
Loading the practice management database.
Ever notice your imaging database pause, freeze, or enumerate before a patient file loads, especially with 3D CBCT scans or large image sets? That's the spinning disk. This shows relative sequential read; on the random I/O a live PMS does, the gap widens to 10 to 100x.
What a dental server should actually have.
Here's the baseline we spec for any new dental server, the minimum for a machine you expect to run for a decade:
OS on mirrored SSDs (RAID 1). Two solid state drives mirrored, so a single drive failure doesn't take Windows Server, and the whole practice, offline.
Data on mirrored SSDs (RAID 1), at a minimum. Dual data drives mirrored so your database and imaging survive a drive failure with no downtime and no restore.
A real hardware RAID controller. Dell PERC, the Lenovo equivalent, HPE Smart Array, whatever your server vendor's card is. A dedicated RAID card, not motherboard or software fake-RAID, which is slower and far harder to recover.
Mirroring is the floor, not the ceiling. The point is that both the OS and the data live on solid state, and both are redundant. A single drive failure should be a quiet swap on a Tuesday, not an emergency that closes the office.
You're buying a 10-year decision.
When you buy a server, you're not buying for this year. You're setting the ceiling for the next decade of how that practice runs. The choices made at purchase, the drive type, the RAID, the controller, are the ones you live with the longest and are the most painful to change later.
Retrofitting solid state and RAID into a running server means downtime and a data migration. Specifying it correctly at purchase costs a fraction of that and buys you years of reliability. If you're planning a new server or a replacement, get the storage right first, everything else is easier to upgrade later.
Common questions.
Can't a dental server just run on one big hard drive?
Not well, and not safely. A single drive forces the OS and the database to compete for the same disk, which is the main cause of slow servers. It also has no redundancy: when that drive dies, the practice is down until it's rebuilt from backup. Separate and mirror the storage instead.
Why mirror the OS drive too, and not just the data?
If the OS drive fails and isn't mirrored, the server stops even if your data is safe. You're then rebuilding Windows Server and reconfiguring everything before the practice can run again. Mirroring the OS on two SSDs means a single drive failure doesn't take the server offline.
Is a single SSD enough if it's fast?
Speed is only half the problem. A single SSD fixes performance but still has no redundancy, and SSDs fail too, often with less warning than spinning drives. For a server you want SSDs in RAID 1 so a drive failure is a non-event, not a closed practice.
How long should a new dental server last?
Plan for about 10 years from a server bought today. That only holds if the storage is right up front: SSDs in RAID for both OS and data, on a real hardware RAID controller. Retrofitting later means downtime and a migration, so it's far cheaper to get it right at purchase.
Planning a new dental server?
We size, spec, and configure dental servers to last, with the storage and RAID done right from day one. Serving dental offices across Eastern Ontario.
or send a message
Server lifecycle planning is part of Bytewing managed IT plans. See what's covered.