![]() After a certain period of time, a client, more specifically db provider will raise an Attention event which will signal the query timeout to the Db Server. code decides to cancel the ongoing action, if the action takes more time to finish than expected(defined). One of the reasons can be the “query timeout”, scenario in which the app. The queries executed on client side may be cancelled during the execution after a certain period of time. More about the parameter can be found here. The parameter belongs to the group of Transaction statements along with: IMPLICIT_TRANSACTIONS, TRANSACTION ISOLATION LEVEL and REMOTE_PROC_TRANSACTIONS (deprecated in Sql Server 2014). Is one of the parameters that define the current session behaviour. Here is a bit of theory we need to know in order to understand the test results. The tests covered a Desktop -SSMS and a web application. The performed tests demonstrate the behaviour of a typical stored procedure when executed in a session with the XACT_ABORT set to ON/OFF and in the query timeout situation. I also briefly covered MARS(Multiple Active Result Sets) technology and how it relates to XACT_ABORT. It is particularly interesting to see how Sequel works with the web applications that use the connection pooling mechanism in those conditions. In this blog I have explored how XACT_ABORT setting controls Sql Server behaviour when it interacts with Desktop and Web applications, in the situation of a query timeout runtime error.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |