Claus Pedersen
Member³
Using column totals in SQL window severely slows down performance.
I have a table with a couple of thousand records. I apply column totals to a number column (average) and a varchar2 column (count).
This can result in a query that fetches approx. 13 rows a second (the speed goes down to fetching approx. 3-4 rows a second when the last rows are fetched) compared to 400 rows a second when column totals are off.
Sometimes the Break button is never enabled during the query, so the only way to kill the query is to kill PLD using the task manager.
I have a table with a couple of thousand records. I apply column totals to a number column (average) and a varchar2 column (count).
This can result in a query that fetches approx. 13 rows a second (the speed goes down to fetching approx. 3-4 rows a second when the last rows are fetched) compared to 400 rows a second when column totals are off.
Sometimes the Break button is never enabled during the query, so the only way to kill the query is to kill PLD using the task manager.