I just stumbled across the following SQL 2005 code:

BEGIN TRY
UPDATE [tabProgramSite]
SET
[Name] = @ProgramSiteName
WHERE [ProgramSiteID] = @ProgramSiteId
END TRY
BEGIN CATCH
END CATCH

Nothing like catching an error… and doing nothing about it. I hope the user experience isn’t as robust.

. . .

→ Read More: Bad Programming: How not to use try/catch blocks