Modernization is often presented as a destination: Move an application to containers, adopt Kubernetes, and become cloud-native. Reality and appetite are usually more nuanced than that. They start with existing infrastructure, business-critical databases, established processes and applications that cannot all be transformed at once. For Microsoft SQL Server customers, this means modernization is rarely a single technical decision.

An organisation might choose to run SQL Server directly on Red Hat Enterprise Linux (RHEL), migrate its existing SQL Server virtual machines (VMs) to Red Hat OpenShift Virtualization, or deploy containerised SQL Server workloads on Red Hat OpenShift. Each route solves a different problem. They do not have to be treated as competing or mutually exclusive choices. In other words, you don’t need to commit to a single option. Exploring one option doesn't lock you in forever, and you can iterate through them depending on where you are in the customer journey.

For organisations that want to retain a traditional server-based deployment model while moving away from Windows Server, SQL Server can run directly on RHEL. This is primarily an operating system modernization path. The SQL Server workload remains familiar, while RHEL provides a supported enterprise Linux foundation. Microsoft supports production SQL Server deployments on RHEL, with support options available for enterprise database environments. This approach may suit organisations that want to standardize more of their infrastructure on Linux without introducing a Kubernetes platform.

Many organisations have substantial SQL Server estates running in VMs. These databases may be connected to legacy applications and availability requirements that have developed over the years. OpenShift Virtualization allows organisations to create, deploy, and manage VMs through OpenShift while running alongside containerised applications on the same platform. This creates a practical first step for customers that want to modernize their infrastructure without immediately changing the way SQL Server itself is packaged and operated.