Forum Discussion
N/A
N/A
You would need to have a separate query for each table that you want to end up in Power BI. Use the same join conditions and where clause for each query, just change the columns that you select to only give the columns you want in that particular table.
Both methods worked correctly, which one is better from a star schema perspective?
Is that the only possible way? Without the query total size is 150MB but with the separate query it's 200 MB size which is a bit strange . I am guessing even with the increase size from seperate query the performance should be better than having them all in one table?
3 Replies
You would need to have a separate query for each table that you want to end up in Power BI. Use the same join conditions and where clause for each query, just change the columns that you select to only give the columns you want in that particular table.
Both methods worked correctly, which one is better from a star schema perspective?
Is that the only possible way? Without the query total size is 150MB but with the separate query it's 200 MB size which is a bit strange . I am guessing even with the increase size from seperate query the performance should be better than having them all in one table?Yes, the increase in size shouldn't affect performance enough to offset the benefits of having a proper star schema