Why are open transactions showing up in SQL Server on idle sessions when I use a SQL Alchemy Engine and connection pooling to connect from Python?
I have a web application built with Python and Flask, and I’m trying to use SQL Alchemy to manage connection pooling for my connections to SQL Server.
Since implementing this, we had an event where our SQL Server maxed out on memory and a bunch of applications and data-refreshes across our company crashed–so now we’re very seriously looking into whether the connection pooling setup led to this overload.
Why are open transactions showing up in SQL Server on idle sessions when I use a SQL Alchemy Engine and connection pooling to connect from Python?
I have a web application built with Python and Flask, and I’m trying to use SQL Alchemy to manage connection pooling for my connections to SQL Server.
Since implementing this, we had an event where our SQL Server maxed out on memory and a bunch of applications and data-refreshes across our company crashed–so now we’re very seriously looking into whether the connection pooling setup led to this overload.
Why are open transactions showing up in SQL Server on idle sessions when I use a SQL Alchemy Engine and connection pooling to connect from Python?
I have a web application built with Python and Flask, and I’m trying to use SQL Alchemy to manage connection pooling for my connections to SQL Server.
Since implementing this, we had an event where our SQL Server maxed out on memory and a bunch of applications and data-refreshes across our company crashed–so now we’re very seriously looking into whether the connection pooling setup led to this overload.