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.
We use Alteryx extensively in my organisation. Most of our data resides in SQL Server 2016. We picked up that in-db queries that are cancelled by the user do not necessarily cancel on the server. We had a couple of rogue queries that filled up the temp space even after the user cancelled the workflow.
This means that one only notice there is an issue if the server starts taking strain.
Has anyone come across this and is there a solution? Our users do not have DBA access so they would not monitor their queries to know when this happens.