Error not raised as I expect

Question

Error not raised as I expect

Viewing 5 posts - 16 through 19 (of 19 total)

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

Jamie Thomson SSChampion Points: 11805 More actions · Answer 1

Point taken about checking for 1 instead of 0 however that would mean changing the behaviour in a system that currently contains over 1000 SPs. So I might leave that to another time!!!

Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson

noeld SSC Guru Points: 96590 More actions · Answer 2

>>Apparently you are running with ANSI_NULLS = OFF.<<

Which is the right thing to do!

I wouldn't recommend to change that setting

* Noel

ron k SSCertifiable Points: 6103 More actions · Answer 3

I would like to correct my previous statement. I did some testing and it appears that in the case of a "severe" error causing the proc to abort the return value is just not set at all and just contains its prior value.

So ensuring that it is set to a value that indicates a failure prior to executing a proc would, as pointed out, be necessary.

ron k SSCertifiable Points: 6103 More actions · Answer 4

Noel,

Why do you say it is correct to have ansi_nulls set to OFF?

ron

noeld SSC Guru Points: 96590 More actions · Answer 5

Actually I have to take that Back! My mistake!

It should have been ansi_nulls should always be set to ON. And the reason I posted that was because I was thinking on the standard SQL 92 that recommends it but I posted the Opposite Looks like I need more COFFEE

Sorry about that.

* Noel