How should the architect implement database high availability in SQL Server?

SQL Server Mirroring provides a high-availability solution for a single user database, maintaining a synchronized copy (mirror) that can be quickly brought online as the principal database in case of a failure, offering automatic failover and transaction-level redundancy.

SQL Server replication is primarily a data distribution technology used for copying and synchronizing data between databases, not a real-time high-availability solution for immediate failover.

SQL Server log shipping involves periodically backing up and restoring transaction logs from a primary to one or more secondary databases, providing disaster recovery but not automatic, near-instantaneous failover for high availability.

Hypervisor high availability (e.g., VMware HA, Hyper-V Failover Clustering) ensures the availability of the virtual machine running SQL Server, but it does not provide database-level high availability or protect against database corruption or logical failures within the SQL Server instance itself.