SQL Serve cursor still alive
Posted: Tue 03 May 2016 14:46
Hello,
using UniDac 6.2.10, is there a way to know if (and, icing on the cake, how much) query cursor are still alive.
I mean, if I have a query that should return more than 25 records (default fetch packet size), and the cursor is server side, SQL Server will not allow to start a transaction until the query is closed or fully fetched.
I would add a test in my code to check if some queries will avoid transaction opening.
Is it possible?
using UniDac 6.2.10, is there a way to know if (and, icing on the cake, how much) query cursor are still alive.
I mean, if I have a query that should return more than 25 records (default fetch packet size), and the cursor is server side, SQL Server will not allow to start a transaction until the query is closed or fully fetched.
I would add a test in my code to check if some queries will avoid transaction opening.
Is it possible?