At the site where I am working now ...
There are multiple places in calling and called procedures where "set
arithabort numeric_truncation" is turned off and back on again.
Each proc that turns it off, then turns it back on again after it
exists, meaning that the calling proc no longer has the setting it
expects.
Is there a way to determine in T-SQL the state of this global
setting? So that I can have a called proc know enough to leave it off
when exiting, like I could for transactions using @[EMAIL PROTECTED]
