Forum Discussion
Advocate IGroup By on (very) large table
andershh When connecting to Oracle database you have an option to write SQL query. So in my opinion it is better option to bring data in the format required through SQL and let Oracle processing happen on the database as you've already mentioned.
Another option is to use R script within query editor. So only dataset is imported in power bi desktop, run R script to perform grouping via Run R Script option which adds R step to the applied steps. I think that would be second best option as R is very powerful in performing this type of operation and you will notice less amount of time being spend on grouping.
Community Championandershh When connecting to Oracle database you have an option to write SQL query. So in my opinion it is better option to bring data in the format required through SQL and let Oracle processing happen on the database as you've already mentioned.
Another option is to use R script within query editor. So only dataset is imported in power bi desktop, run R script to perform grouping via Run R Script option which adds R step to the applied steps. I think that would be second best option as R is very powerful in performing this type of operation and you will notice less amount of time being spend on grouping.
Advocate Iankitpatira - Thank you for taking the time to try and help me! I think the SQL idea is very good (to be honest I hadn't noticed the option when connecting to a data source). However, since I am using the same Oracle connection for other PowerBI reports and data tasks - I haven't been able to add a duplicate connection to the database with the SQL inserted. If I change the configuration of the Oracle data source, then I will change it for all my Power BI reports that utilizes it - right?
Nevertheless, if this hadn't been the case I am certain your suggestion would have been an excellent solution - I am therefore marking this a solution.
AlexChen - Also a big thank you to you for taking the time to write a thorough reply. I have moved forward with the third option I specified in the original. I think your suggestion for fixing the table is spot on - however I do not have the admin rights to the database (I can only extract data from it), so I can't utilize your excellent suggestion. But many thanks nevertheless!