GOTO Statement

Question

Post reply

GOTO Statement

AndrewSQLDBA

SSC-Insane

Points: 21827
More actions
January 12, 2010 at 7:33 am

#219141

Hello Everyone
After diving head first into a multi database application. I am seeing the previous developer had used GOTO statements for errors.
I thought I had read that GOTO was not going to be supported any longer. Does anyone have a site or docs that tell what items, objects, data types, syntax will no longer be supported and removed.
Thanks
Andrew SQLDBA

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

OTF SSCertifiable Points: 6104 More actions · Answer 1

http://msdn.microsoft.com/en-us/library/ms143729.aspx

Paul White SSC Guru Points: 150467 More actions · Answer 2

Clickable version of that link:

Deprecated Database Engine Features in SQL Server 2008

GOTO is part of the T-SQL language and probably always will be. It can be quite useful, and there's nothing wrong with it if not abused 🙂

Paul

Paul White
SQLPerformance.com
SQLkiwi blog
@SQL_Kiwi

mtassin SSC-Insane Points: 23099 More actions · Answer 3

Seeing as this is in the SQL 2k5 forum.

Personally if you have the time, I'd look at converting the GOTO's to TRY/CATCH blocks.

Just so much simpler to be able to handle specific errors with every operation if necessary and write specific error handling right there with the potential error causer.

If you don't have the time... the GOTO logic will never leave us :/

--Mark Tassin
MCITP - SQL Server DBA
Proud member of the Anti-RBAR alliance.
For help with Performance click this link[/url]
For tips on how to post your problems[/url]

Conan The Canadian Ten Centuries Points: 1335 More actions · Answer 4

mtassin (1/14/2010)
Seeing as this is in the SQL 2k5 forum.
Personally if you have the time, I'd look at converting the GOTO's to TRY/CATCH blocks.
Just so much simpler to be able to handle specific errors with every operation if necessary and write specific error handling right there with the potential error causer.
If you don't have the time... the GOTO logic will never leave us :/

TRY/CATCH shouldn't be the only error checking that you do (but should be in there!).

You could run into a scenario where you run an update which executes fine but doesn't update any records. You might want some error checking to verify that *something* was updated if you require such a condition.

Kev -=Conan The Canadian=-
@ConanTheCdn