SQL Server not connected after windows 11 update

Question

I've local database in my laptop and used to connect through SSMS version 18. After updating to windows 11, i am unable to connect SQL server.

Answer 1

Step one: confirm the service is running

If yes, then step 2:

(a) try to connect using PowerShell using the command Invoke-Sqlcmd

(b) try to connect using sqlcmd

let's confirm that the issue related to the SSMS or to connection in general

Inform us i this solve your issue and if not then report the result and if you hav more information then please provide it

A side-note! IT IS VERY BAD IDEA (in my opinion) TO UPGRADE THE HOST WHILE SQL SERVER EXISTS. UPGRADE version of OS or SQL Server is not a daily work and it is usually done after your system already running for long time. I highly recommend next time to start from scratch (install OS -> install SQL Server). In general, I am against upgrading and recommend to use the opportunity to re-design the system and and work on clean system.

Answer 2

SQL Server is not yet officially supported on Windows 11. Questions like this one suggest there's an incompatibility on some systems with the way Windows 11 reports physical sector size of some SSD devices, although I personally have no issues on my workstation with a fresh Win 11 and SQL Server 2019 install and similar configuration.

Check the SQL Server error log for error messages. Also, run this command from an administrator command prompt and post the output:

fsutil fsinfo sectorinfo c:

Answer 3

Do you have related messages in the SQL Server error log? The default error log location with Developer Edition is C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\errorlog or
C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Log\errorlog with Express Edition. I expect you will see errors related to misaligned sector IOs because Windows 11 is not reporting the correct values for PhysicalBytesPerSectorForAtomicity and PhysicalBytesPerSectorForPerformance. 32768 is wrong; expected values are 512 or 4096. SQL Server performs low-level sector-aligned IO and values outside the expected range will cause problems with data/log file IO.

Albeit currently unsupported, SQL Server 2019 does run on my Windows 11 machines (desktop and laptop). The desktop was a fresh Windows 11 and SQL Server install and the laptop was an upgrade from Windows 10 with SQL Server already installed like your situation. Both report 4096 for PhysicalBytesPerSectorForAtomicity and PhysicalBytesPerSectorForPerformance. I suspect the incorrect sector value reporting by Windows 11 occurs only on certain hardware (maybe firmware too) configurations.

You'll need to install on a drive with a 512 or 4096 sector sizes (physical or virtual). Alternatively, use a VM, or use a Docker SQL Server container instead. These methods will report correct sector information. Uninstalling on Windows might be a problem as in this question. I don't have a non-working Windows 11 SQL Server installation to test the uninstall myself.

Answer 4

Here is a solution at the end of the post that may work for you. I experienced a similar problem. Maybe this helps? Good luck.

https://learn.microsoft.com/en-us/answers/questions/668708/ssd-showing-incorrect-bytes-per-sector-win-11-sql.html?childToView=670292#answer-670292