This content has been marked as final. Show 5 replies
Why dont you make it as a store procedure and return your result as an array?.
> wow, 36 QoQs... sure you can't do it all in one query with some creating
> SQL and GROUP BY clause???
Seconded. I think the first thing that needs explaining is why there are
36 queries to start with.
My wish is to have a query that returns me something like that
ID | result1 | result2 | ... | result36
84 8.12 6.48 7.69
An array might be simpler.
Are you sure you need 90K rows? That slows down production big time. If it's historical data that's never going to change it might be worth the time and effort to summarize it in your db.
I completely changed my mind...
I do not have the rights to create a SP.
The data I retrieve is updated every month ...
What I do... run the big query, export data to a csv file,
import the csv into a SQL database and then I run a SP from my SQL server... it does the job so...thank you for you ideas anyway !