raiserror level

Question

raiserror level

Steve Jones - SSC Editor

SSC Guru

Points: 734416
More actions
October 1, 2014 at 8:37 pm

#72517

Comments posted to this topic are about the item raiserror level
October 2, 2014 at 2:23 am

This was removed by the editor as SPAM

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

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

Eirikur Eiriksson SSC Guru Points: 182879 More actions · Answer 1

Thank you for the question Steve.

Slightly off topic, prefer using RAISERROR to PRINT for progress reporting on long running scripts as it is almost instant and the printf functionality is very handy.

RAISERROR ('This is %s message number %d!', 0, 0 ,'my',123) WITH NOWAIT;

😎

SQLWinther SSCertifiable Points: 6294 More actions · Answer 2

Eirikur Eiriksson (10/1/2014)
Thank you for the question Steve.
Slightly off topic, prefer using RAISERROR to PRINT for progress reporting on long running scripts as it is almost instant and the printf functionality is very handy.
RAISERROR ('This is %s message number %d!', 0, 0 ,'my',123) WITH NOWAIT;
😎

I totally agree with you.

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

Ed Wagner SSC Guru Points: 287024 More actions · Answer 3

Thanks for a a good question. I also use instead of print to avoid the delay associated with print, especially when debugging. I find the core functionality to be excellent as well, especially when I have several independent (albeit related) steps in a process. I can throw an error to display some information that a step won't be processed and the continue on with the rest of them.

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

SqlMel SSCrazy Points: 2901 More actions · Answer 4

Good question, Steve. Thanks.

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

Raghavendra Mudugal SSChampion Points: 10658 More actions · Answer 5

Thank you for the post, Steve, good one.

Well, this was bit challenging one for me especially when you are working in cmd mode, but after generating few errors manually via script and few minutes of analysis, I marked the answer with 70-30, and I got it right. 🙂

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

Dana Medley SSCertifiable Points: 6764 More actions · Answer 6

Thanks for the question Steve.

Everything is awesome!

SQLRNNR SSC Guru Points: 281334 More actions · Answer 7

Useful information imho. It would be nice to have the msdn article on the topic clarified a bit.

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

Kick6Tiger SSCrazy Points: 2380 More actions · Answer 8

Nice question, I like when I have to Google to find the answer.

Aigle de Guerre!

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

Thanks for the question, Steve.

Using RAISERROR to generate messages is a good idea; I'll have to remember that. One more item in the ol' bag o' tricks!

Miles Neale SSChampion Points: 13147 More actions · Answer 10

Nice to know. Thanks!

Not all gray hairs are Dinosaurs!

Steve Jones - SSC Editor SSC Guru Points: 734416 More actions · Answer 11

Note that THROW works well in some cases, RAISERROR in others.

Learn how to use both.

akljfhnlaflkj SSC Guru Points: 76202 More actions · Answer 12

The key for me was the word informational. Those go through 10.

akljfhnlaflkj SSC Guru Points: 76202 More actions · Answer 13

Dana Medley (10/2/2014)
Thanks for the question Steve.

I love your bug avatar. It fooled me. I thought there was a bug on my screen.