If a parent connection repeatedly runs a query that uses intra-query parallelism, several INT: EXCHANGE child connections may be spawned and then dropped each time the query runs.
This is not easy to observe while the loop is running since the INT: EXCHANGE connections all look the same... except for the fact the connection numbers grow by leaps and bounds, and there may be gaps when short-lived child connections go completely unnoticed.
Is there a cumulative count of child connections available? Such a counter might help to highlight an abuse of intra-query parallelism.
(if not, consider this a request).
There is no connection counter that tracks this information currently. Enhancement request noted.
answered 31 Mar '16, 16:17