I asked a two-part question on Twitter: if you could only remove one feature from SQL, why would it be cursors?
If you could only remove one feature from SQL, why would it be cursors?
— Brent Ozar (@BrentO) January 20, 2021
The responses were great:
Auto-shrink does not agree
— Warner Chaves (@warchav) January 20, 2021
service broker, bro.
— ? Andy Mallon #BlackLivesMatter (@AMtwo) January 20, 2021
— Gianluca Sartori (@spaghettidba) January 20, 2021
Because SQLCLR was too popular.
— Marc Gravell (@marcgravell) January 20, 2021
— Gail Shaw (@SQLintheWild) January 20, 2021
Merge statement for me
— Justin Bird ??????? #mtfbwy (@jbmetricy) January 20, 2021
Justin’s referring to MERGE’s hot mess.
Hmmm, cursors or triggers? ?
— DapperDweeb (@DapperDweeb) January 20, 2021
Can we add linked servers to this list?
— Timmy the SQL (@TimmySQL) January 20, 2021
my personal pain point in SQL Server: OLE Automation.
All OA Objects are bad, but especially "in process" OLE objects.
CLR bothers me too, but CLR is not not OA bad.
Cursors are just garden grade evil. They annoy me, but I have seen use cases that support cursors.
— Pat Phelan (@YetAnotherSQL) January 21, 2021
But out of all of ’em, this one intrigues me the most:
SSAS, SSRS(almost there on that one), not sure about SISS. Make em seperate products and lower the price of SQL server editions.
— John Cas (@moresunshine_1) January 21, 2021
How about you?