Interface Guide
SATA, SAS and NVMe describe how a drive talks to the server — not how fast the NAND inside it is. Choosing the wrong one wastes money on a drive the chassis cannot use, or buys more performance than the workload needs. Here is how the three compare in practice.
The short version
| Interface | Best for | Watch out for |
|---|---|---|
| SATA | Boot volumes, read-heavy servers, older controllers | Single path, ~6Gb/s ceiling |
| SAS | Enterprise arrays, dual-path redundancy | Requires SAS controller and backplane |
| NVMe (U.2 / E3.S) | Databases, virtualisation, hot tiers | Needs Gen4/Gen5 lanes, correct bay and cabling |
SATA: the compatibility baseline
SATA SSDs remain the lowest-friction option. They fit standard 2.5-inch hot-swap bays, work with almost every controller built in the last decade, and are usually the cheapest per terabyte at a given endurance class. The ceiling is the interface: roughly 6Gb/s, shared per port.
For boot drives, log volumes and read-heavy application servers, SATA is often the rational choice. The mistake is assuming it can absorb write-heavy workloads just because the drive is “enterprise”.
SAS: redundancy and enterprise plumbing
SAS drives offer dual-port connectivity, which matters when a single cable or expander failure should not take a drive offline. They also support deeper queueing. The price is complexity: a SAS controller, the right backplane and cabling, and usually a higher unit cost.
SAS SSDs are common in enterprise arrays where the enclosure was designed around SAS. If you are replacing drives in such an array, the interface is already decided — match it.
NVMe: performance, but check the plumbing
NVMe removes the legacy storage stack and attaches drives directly to PCIe. In a modern server the difference is substantial for random reads and mixed workloads. But NVMe is a family of form factors, not one connector:
- U.2 — 2.5-inch bay, PCIe lanes routed through the backplane
- U.3 — newer bay standard, often backward compatible with U.2
- E3.S — smaller, higher-density form factor on newer platforms
- M.2 — common in client devices, increasingly used for boot in servers
Before ordering NVMe, confirm the server generation, the number of available PCIe lanes, and whether the bays are actually wired for PCIe rather than SATA/SAS.
Endurance matters more than the interface name
Two NVMe drives with the same capacity can differ by an order of magnitude in write endurance. Read-intensive drives are typically rated around one drive-write-per-day; mixed-use and write-intensive drives cost more but tolerate sustained writes.
Match the endurance class to the workload: a read-mostly web tier does not need a write-intensive drive, and a write-heavy logging tier should not be handed a read-intensive one to save money.
Checklist
- Confirm the bay type and whether it is wired for SATA, SAS or PCIe
- Confirm the controller supports the interface and the drive capacity
- Match endurance class (DWPD/TBW) to the workload
- For refurbished drives, request SMART wear data before dispatch
- Confirm power-loss protection if the workload is write-critical
Ask us to match a drive to your server
Related