Hello,
I noticed there is a similar question for Npgsql here, but I am unsure if it also applies to Azure SQL Server.
In our scenario, we call SQL Server to query data twice in one transaction for 99.5% of cases. If we use BeginTransaction() and Commit(), it will require four roundtrips, which nearly doubles the latency in the transaction part.
Are there any concerns if we choose to explicitly set transaction isolation with SNAPSHOT and use BEGIN TRAN and COMMIT TRAN within CommandText? Additionally, do you have any suggestions or best practices that could help us optimize the performance and reduce latency during these transactions? Any insights from your experience would be greatly appreciated.
Hello,
I noticed there is a similar question for Npgsql here, but I am unsure if it also applies to Azure SQL Server.
In our scenario, we call SQL Server to query data twice in one transaction for 99.5% of cases. If we use BeginTransaction() and Commit(), it will require four roundtrips, which nearly doubles the latency in the transaction part.
Are there any concerns if we choose to explicitly set transaction isolation with SNAPSHOT and use
BEGIN TRANandCOMMIT TRANwithin CommandText? Additionally, do you have any suggestions or best practices that could help us optimize the performance and reduce latency during these transactions? Any insights from your experience would be greatly appreciated.