SET XACT_ABORT On By Default

Tibor Karaszi notes an important change to SQL Server Management Studio with the July 2016 release:

Now, exposing one more SET option can’t be bad, right? But Erland Sommarskog found out that this is checked by default. Now, using XACT_ABORT might now [sic] be a bad thing, au contraire. See this one of Erland’s series of error handle articles.

Making this change after all of these years is a little odd.  Making it in a regular update is very odd.  Using SET XACT_ABORT ON is a smart move in general, but there are times in which you don’t want to rollback immediately after an error; the problem is, are all of those places in your code well-documented?

Related Posts

R Services 182 Error

Joey D’Antoni provides a solution to a tricky SQL Server R Services error: Recently, and unfortunately I don’t have an exact date on when this started failing (though it was around service pack 1 install time) with the following error: Error Msg 39012, Level 16, State 1, Line 10 Unable to communicate with the runtime […]

Read More

Tracking Database Restoration-Related Errors

Adrian Buckman has a script which tracks error messages related to database restorations: In one of my previous posts I went over a scenario where an Auto restore job was logging Restore errors to a table and the error that was being inserted was ‘3013 – RESTORE LOG is terminating abnormally’ and this was due to SQL Server […]

Read More

Categories

July 2016
MTWTFSS
« Jun Aug »
 123
45678910
11121314151617
18192021222324
25262728293031