Share via
Tamizhiniyan Natarajan 1Reputation point
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.
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,332 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
10,470 questions
Sign in to follow
0{count} votes
AmeliaGu-MSFT 13,986Reputation points • Microsoft Vendor
2021-12-07T05:55:42.32+00:00 Hi TamizhiniyanNatarajan-3801,
How are things going? Was your issue resolved?
If you find any post in the thread is helpful, you could kindly accept it as answer.
If not, please don't hesitate to let us know and provide us with more information about your issue.Best Regards,
AmeliaTamizhiniyan Natarajan 1Reputation point
2021-12-08T11:57:53.117+00:00 Still having issue.
Sign in to comment
4 answers
Sort by: Most helpful
Most helpful Newest Oldest
Ronen Ariely 15,196Reputation points
2021-12-03T15:24:55.593+00:00 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.
0 commentsNo comments
Sign in to comment
Dan Guzman 9,251Reputation points
2021-12-03T15:30:28.507+00:00 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:
Tamizhiniyan Natarajan 1Reputation point
2021-12-04T04:10:34.79+00:00 Here is the output i get it from cmd prompt
LogicalBytesPerSector : 512
PhysicalBytesPerSectorForAtomicity : 32768
PhysicalBytesPerSectorForPerformance : 32768
FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096
Device Alignment : Aligned (0x000)
Partition alignment on device : Aligned (0x000)
No Seek Penalty
Trim Supported
Not DAX capable
Not Thinly-ProvisionedDan Guzman 9,251Reputation points
2021-12-04T19:27:08.023+00:00 Can you share the make and model of your SSD storage?
Tamizhiniyan Natarajan 1Reputation point
2021-12-07T16:29:09.167+00:00 SAMSUNG MZALQ512HBLU-00BL2
Sign in to comment
Dan Guzman 9,251Reputation points
2021-12-04T14:41:03.713+00:00 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
orC:\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.
Tamizhiniyan Natarajan 1Reputation point
2021-12-07T16:43:55.443+00:00 Thank you. But i could see my ssd sectior is 512.
Error which i am getting is,
There have been 256 misaligned log IOs which required falling back to synchronous IO.Dan Guzman 9,251Reputation points
2021-12-14T11:01:23.7+00:00 @Tamizhiniyan Natarajan , PhysicalBytesPerSectorForAtomicity and PhysicalBytesPerSectorForPerformance both show 32768. These need to be 4096 or less. Another workaround you can try is to start SQL Server with trace flag 1800.
Sign in to comment
DR 46Reputation points
2021-12-20T22:38:21.203+00:00 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
0 commentsNo comments
Sign in to comment
Sign in to answer