MacOS

Under the Hood of the Azure SQL Database Container: Native ARM64

Today at Ignite, Microsoft announced the public preview of the Azure SQL Database container. The line in the announcement that jumped out at me was this one: the container runs natively on x64 and ARM64, including Apple Silicon. If you’ve been following along with my posts on running SQL Server on Apple Silicon and the AVX issue under Rosetta, you know I’ve been waiting a long time to type that sentence.

So I did what any reasonable person would do on announcement day. I pulled the image, started it up next to a SQL Server 2025 CU11 container on my M4 Pro, and started taking both of them apart. I wanted to know two things. First, how did Microsoft get a SQL engine running natively on ARM64? Is it emulation? A brand new engine? Second, how does a container on my laptop pretend to be a managed cloud service?

SQL Server 2025 CU1 Fixes the Docker Desktop AVX Issue on macOS

Good news for anyone who’s been working around the AVX issue I wrote about in my previous post. Microsoft has fixed it in Cumulative Update 1 (CU1) for SQL Server 2025.

What Changed

Back in November when SQL Server 2025 RTM was released and I upgraded to macOS 26, I ran into an AVX instruction issue that prevented the container from starting on Docker Desktop using Rosetta on Apple Silicon. The container would crash with this error:

Getting SQL Server 2025 RTM Running in Containers on macOS

Update (February 2, 2026): Microsoft has fixed this issue in SQL Server 2025 CU1. The container now runs successfully on Docker Desktop for macOS without needing OrbStack. See my follow-up post for details.

SQL Server 2025 RTM is here, and if you’re running Docker on macOS Tahoe 26, you might have hit a wall trying to get it running. Here’s what happened when I tried spinning up the latest container image and how I worked around it.