Fair point but this wouldn't work if your SP was kicked of by another server process (say, a batch job).

I do generally dissagree though... you should always have error handling in your procedures.

It's true that serious errors just kill the procedure before your error handler kicks in and you need to cater for that, but if you properly construct your error handler it can return some valuable info on the cause of what went wrong as you can include data into your error string. You can of course get round that by using output parameters for returning error data but you start getting complexity and defeat the object of not having error handling...

I think you really need a good combination of both techniques.

Sam