This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
At my company, we primarily work out of SQL Server, so to connect to most data requires me to input data with a database connection. Unfortunately anytime I connect to the database, I start getting long-running query/connection alerts from our IT team, and I'm not sure how to prevent that from happening. The workflows I'm creating thus far are relatively simple pulls from the database right at the start (queries lasting no more than a few seconds) so my understanding was that my work in the database was done -- but then 30 or 45 minutes later I'll get alerts and realize somehow the connection is still open.
Is there a way to ensure that your connection gets closed when the workflow finishes running? I already tried one recommendation on the board (Disable Auto Configure), and that hasn't prevented the connection from staying open.
You're not alone with this issue. The connection will stay open until the instance is closed. Not only will the connection remain open, but the connection count can be multiplied by the quantity of records going into a Dynamic Input tool.
I haven't tried this myself, but another suggestion I came across was to write a SQL statement to force close connections and execute it with the Post SQL statement option of the Input tool.