December 2, 2019 at 12:00 am
Comments posted to this topic are about the item Getting the Options
December 2, 2019 at 6:09 am
Nice, easy question to start the week on, thanks Steve
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
December 2, 2019 at 2:05 pm
Thanks for the question, Steve! This was fresh on my mind after having recently read jonfrisbee's article on the subject.
December 2, 2019 at 2:58 pm
Now, all those in the room that have actually used this function in production, please raise your hand! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 2, 2019 at 10:20 pm
I've used it to troubleshoot, wondering if two connections had different settings. Getting a raw number and comparing them worked for me. I haven't really used this to decode settings in production.
December 3, 2019 at 5:51 am
I've used it to troubleshoot, wondering if two connections had different settings. Getting a raw number and comparing them worked for me. I haven't really used this to decode settings in production.
Thanks, Steve. Haven't had to do such a comparison yet but thanks for the idea. That would certainly make for a quick and easy check.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 3, 2019 at 6:20 am
Now, all those in the room that have actually used this function in production, please raise your hand! 😀
We have a lot of legacy code that was written loooong before XACT-ABORT. Most of the newer code uses XACT_ABORT, but sometimes wrapping an older proc causes unexpected results with the error handling and transaction control. So I have had to check whether XACT_ABORT is on, turn it off, wrap the old proc, set XACT_ABORT on again.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply