jimm98y
commented
7 months ago I've been looking into this during the weekend and the problem with the 64bit configuration missing in the UI is that on ARM64 the x64 emulation works differently when compared to x86. The x86 entries are there because mmc.exe runs as x86 process in emulation and it is able to load x86 DLLs (the 32-bit configuration). For x64, there is no x64 mmc.exe on Windows 11 ARM64 - it runs as ARM64 process which cannot load x64 DLLs. I'm not sure why Microsoft decided to compile mmc.exe as ARM64 instead of ARM64EC. Basically to make it work:
- Microsoft would have to recompile C:\Program Files\Microsoft SQL Server\160\Tools\Binn\SqlManager.dll to ARM64, which means officially making ARM64 version of the SQL Server
- Microsoft would have to recompile C:\Windows\System32\mmc.exe to ARM64EC
- We'd have to somehow take x64 mmc.exe from Windows 11 x64 and make it work, but even then the OS would probably fight back and it wouldn't be a seamless experience
So this missing mmc.exe UI means basically that for some supported features we'll have to configure them through Windows Registry.
Installed 2022 Developer successfully on a MBP M3. SSMS installed too without issue. I was able to use the Window Authentication account to enable mixed mode auth with sa and pw.
My primary issue is that SQL Server Configuration Manager only shows the 32bit entries (64bit missing). This may be expected in this environment but prevents access to the server configuration such as changing from the default port. Apologies if this is expected and thus not an issue.
My secondary issue now is that Red-Gate SQL Compare v14.10 will not connect to a cloud (AWS) server. It fails with a failed "named pipes" connection even though I am clearly using an alias that uses TCP. SSMS can connect to the same cloud server with the same alias without issue. Again, I worry that the SQL Compare product is requiring the missing 64bit Alias in SSCM definition but I cannot set it. Not smart enough to know of these are related but just suspect.