Currently Fabric does not support SET XACT_ABORT ON.
We request to add this support to reduce breaking changes when migrating and to improve transaction support for the scenario below
This results in a breaking change in how transactions are handled and makes Fabric behave differently to other editions like
- SqlPool (Dedicated)
- SqlDbEngine
As an example consider this Sproc below
CREATE PROC usp_TranTest
AS
BEGIN
BEGIN TRY
BEGIN TRAN
select * from table_that_doesnt_exist
--Do other Work
COMMIT TRAN
END TRY
BEGIN CATCH
ROLLBACK TRAN
print 'error'
END CATCH
print @@TRANCOUNT
END
GO
exec usp_TranTest
This will result in the following behaviour
Sql Pool (Dedicated): Rollback and zero trancount
Fabric: No rollback and tran leak
On Premise SqlDbEngine: No rollback and tran leak
On Premise SqlDbEngine with SET XACT_ABORT ON: Rollback and zero trancount
So the ask for Fabric DW is when migrating from SqlPool we need one of three things:
- Make engine beghave same way as SqlPool
- or
- Add the option of SET XACT_ABORT, so we can use this for backwards compatibility with SqlPool behaviour.
Or
- Both
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Copy formatting edits/styles across visuals
It would be very helpful if there were a feature that allowed you to copy all the formatting changes from one visual to another, or to apply it to all visuals. This is different to changing the them...Ezraa3217 minutes agoNew MemberNew2Views0likes0CommentsAllow admins to choose the preferred connection type for automatic binding
Currently, when the same data source qualifies for both a Cloud Connection/Personal Cloud Connection (PCC) and an Enterprise gateway connection, Power BI may identify multiple eligible connection can...v-viputta14 hours agoMicrosoft EmployeeNew191Views57likes0Comments