Yeah, like THROW...try putting one in a BEGIN/END block and see SQL Server complain.

To err is human. To really foul up - it takes a computer.

I have seen it said that EXISTS/NOT EXISTS can be faster because it can "short circuit". That is, as soon as it find a case satisfying its condition, it's done,...

I used to have an old IBM Selectric keyboard...I loved typing on that thing, my hands must have bounced 6 inches off the keyboard with every touch. I can't say...

And the problem with a stored procedure is that you have to work around Entity Framework (with different code) to get it to work, whereas a view appears to EF...

If you're using Entity Framework (not EF Core) I'd consider using a view, not a stored procedure, for the select. If you shape the view the way the entity expects...

I kinda disagree with #27 and 30, though I guess it depends on what version of SQL Server we're talking about. I wouldn't use @@ERROR, I'd use ERROR_NUMBER() and the...