Orphaned Sessions (Zombie Connections) are occuring and some of them causes BLOCKING SESSIONS CHAIN?

  • Hi dears,

    I have a consolidated SQL Server Environment. And main OLTP Databases was developed with Linq, Entity-Fraremwork. All Connections come through to the database with SERIALIZIBLE ISOLATION Transactions. 

    And after the application came live, in our sql server instance; many orphaned(zombie) sessions are occuring. In addition to this situation, several times in a day Blocking sessions are existing in the instance, because of orphaned connections.

    Are Blocking Sessions Chain related with Isolation Levels & Zombie Sessions?

    And Please, let me inform about an unforgotten COMMIT/ROLLBACK Statement causes Zombie Sessions? Or if you have  LINQ Framework knowledge, how do you recover these happenings?

    Waiting your responses...

  • Investigate your common or long running transactions. It is possible that the transactions are running long enough there by not releasing locks. This is one of the common symptoms of Serializable Isolation.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply