SQL Server

Raised as a usability problem by 35 people on Hacker News over 17 years (2010–2026), in 38 threads.

People raised many different problems with SQL Server, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 39 complaints

Scroll indicator is smaller, so the cursor must hover exactly over it to drag2026-01-07
Takes hours to get the required SQL Server tooling working on Windows2025-11-12
Has to relearn the OVER clause every time because the API doesn't make sense2025-04-09
Spent over a week struggling with missing docs and obscure setup to get a connection string working2024-04-22
Bloated, kitchen-sink interface that feels slow to use2023-07-07
SSMS is slow to open, and Azure Data Studio is slower and unreliable otherwise2023-04-19
Editor keeps showing tab A's text after switching to tab B until scrolled or edited2021-10-29
IntelliSense autocomplete is unreliable compared with Visual Studio's2021-08-29
Interface is clunky, and it reported SSL certificate configuration as not applied when it was2021-02-12
Some context menus have hardcoded black text, so they are hard to read in dark mode2020-10-31
MERGE is not atomic without non-standard hints, forcing developers to manage locks and transactions2020-09-04
No instant search or filter through query results, unlike third-party clients2020-04-19
Management tool is a usability nightmare, hard to find better alternatives2020-04-03
With Azure SQL, SSMS drops users into a raw syntax editor instead of guided dialogs2019-11-20
OK button falls off-screen and the window can't be resized to reach it2019-10-26
Hard to quickly find and manage thousands of stored procedures2019-10-17
Module automatically switches drive to a virtual one when loaded, surprising users2019-05-07
Working with other databases is frustrating after getting used to SQL Studio2019-01-15
Adding a fourth WHERE constraint makes a query run thousands of times slower2018-12-05
Import/export tools are buggy and cumbersome; no simple export of query results to INSERT statements2017-05-09
Installing requires obscure PowerShell commands and a hand-written config file2016-12-19
Installing and configuring SQL Server on Windows needs arcane CLI arguments and PowerShell, a huge pain to automate2016-12-19
Graphical job design is over-engineered and jobs are too brittle to reuse2016-10-10
Default install settings are poor, forcing users to reconfigure before real use2016-06-20
Feature is obscure and has a steep learning curve for users2016-06-09
Installation steps given without explaining why, plus sparse troubleshooting docs2016-01-17
Required significant poorly documented, confusing configuration to work with XML meaningfully2015-05-19
Unclear which options to click during install, leading to two versions side by side2015-05-12
Basically unusable on high-resolution retina display2015-03-25
Installer has about 20 pages of settings that users don't understand, leading to misconfiguration2015-03-09
Installing SQL Server was a mess and it wouldn't recognise a database someone sent2015-03-05
Jumping to a database object takes many expand and filter steps and is error-prone2014-03-06
Powerful but cumbersome and hard to script, stuck in GUI-and-wizard style2014-01-16
Import fails with no indication of where the error occurred, after many GUI steps2014-01-16
Query plan view hides key info like estimated vs actual rows; hard to learn2013-10-02
Silently corrupts data when it guesses wrong instead of rejecting the query2013-03-25
Hard to test properly and suffers deployment problems2012-11-21
Pasting bad rows triggers hundreds of popups, with no way out but killing the process2011-06-22
Installation and upgrade errors happen frequently, taking hours of fighting the installer2010-09-17