THROW defaults

Question

THROW defaults

Steve Jones - SSC Editor

SSC Guru

Points: 736504
More actions
October 4, 2014 at 12:28 pm

#311524

Comments posted to this topic are about the item THROW defaults
October 6, 2014 at 2:17 am

This was removed by the editor as SPAM

Viewing 15 posts - 1 through 15 (of 18 total)

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

Koen Verbeeck SSC Guru Points: 259115 More actions · Answer 1

Interesting question, thanks.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Vimal Lohani SSCommitted Points: 1650 More actions · Answer 2

+1

Vimal LohaniSQL DBA | MCP (70-461,70-462)==============================The greatest barrier to success is the fear of failure ** Success is a journey not a destination**Think before you print, SAVE TREES, Protect Mother Nature

SQLWinther SSCertifiable Points: 6294 More actions · Answer 3

That was an easy question. 🙂 Thank you for that point.

/Håkan Winther
MCITP:Database Developer 2008
MCTS: SQL Server 2008, Implementation and Maintenance
MCSE: Data Platform

TomThomson SSC Guru Points: 104773 More actions · Answer 4

Nice question. But the answer turned up in comments on last weeks raiserror question, so it was a bit easy for anyone who had read that.

Tom

SqlMel SSCrazy Points: 2901 More actions · Answer 5

Arrrrrgggghh.... Had it but then I changed my mind.

Thanks, Steve.

---------------
Mel. 😎

Ed Wagner SSC Guru Points: 287026 More actions · Answer 6

I understand the THROW to match error handling in other languages, but I still use RAISERROR. You get to define you own severity and you can use it in place of a PRINT statement to bypass the buffering of printed messages.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

rhythmk SSCertifiable Points: 7271 More actions · Answer 7

Thanks for question.

--rhythmk
------------------------------------------------------------------
To post your question use below link

https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂

Raghavendra Mudugal SSChampion Points: 10658 More actions · Answer 8

Thank you for the post, Steve, nice one.

(first I saw the options and saw 16 there and then selected it as "cool... sweet 16"... and submitted, then I read the question what this 16 I got it right?.... well, strange beginning of the week :-P)

ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.

SQLRNNR SSC Guru Points: 281334 More actions · Answer 9

Ed Wagner (10/6/2014)
I understand the THROW to match error handling in other languages, but I still use RAISERROR. You get to define you own severity and you can use it in place of a PRINT statement to bypass the buffering of printed messages.

Those are some really nice advantages

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

RK Mandava SSCarpal Tunnel Points: 4153 More actions · Answer 10

Including SQL 2012 (In the Explanation "As of 2014"), The severity is set to 16.

stephen.long.1 SSCrazy Points: 2582 More actions · Answer 11

Thanks for the relatively easy question to start the week, Steve.

Jim_K SSCrazy Points: 2418 More actions · Answer 12

Huh, I wonder why they are limiting throw in 2014? The raiserror documentation says to prefer throw, but it's less capable. I'm wondering if they want you to use sp_addmessage to define errors with a different severity...

Miles Neale SSChampion Points: 13147 More actions · Answer 13

Thanks, and it shows the value of taking time to look at what is said in the comments on questions. Taking what was said last week this was easy.

Not all gray hairs are Dinosaurs!