Forum Discussion
Power BI Report Size Increase with Different Queries Despite Having the Same Amount of Data
Super UserI use a 'TableA' stored in a SQL Server Data Warehouse.You mean a SQL Server database?
I have another table 'TableB', which is created by performing some transformations to TableA thanks to an ETL process. I hope to be able to replicate this ETL job of TableB in PowerQuery and thus avoid storing this table that occupies 90% of my DB.In general, performance on SQL Server is substantially better (sometimes orders of magnitude) than Power Query.
Storage is cheap. Get some more storage on your database server, and run as much of the processing there.
(You could use a view to avoid materializing the TableB but that comes with the penalty that you can't spool the data any more.)
Yes, I currently have both table A and table B in SQL Server. These are written daily with a Talend process.
Table B is written using table A in a Talend job. The idea is just to be able to eliminate Table B from the Data Warehouse and the Talend job since they take up 90% of the storage in the Data Warehouse and a part of all the time of the ETL process.
That is why I have tried to replicate this job but in PowerQuery with the long query making use of table A directly. In the end, the resulting number of rows and columns is the same, but the file size is much larger, and I don't know the exact reason for this.
- lbendlin
Table B is written using table A in a Talend job.Why? Why not do that directly in SQL Server?