Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
gregboothdelt
Helper I
Helper I

How to do advanced data manipulation in Power Bi

We were hoping to pull some data into a data warehouse staging area- so we could do a lot of manipulation of the data. The resulting data would be made available for querying in power bi.

However, for the main data source we can only import this data into power bi (we cannot connect an ETL tool to it).

So all the maniuplation/data prep will need to be done in power bi - but i am not sure if this will be possible.

For example , for each record, there is some coordinates. We need to martch this to the nearest house. We were going to do this as part of the ETL build phase using T-SQL. 

Is it realistc that we even think about doing this in Power Bi itself (for example using power query).

1 ACCEPTED SOLUTION
lbendlin
Super User
Super User

Depends.  Power Query is a very powerful language, and it can do a lot of nifty ETL things. But it's not comparable with SSIS or Informatica etc. You will run into performance issues when dealing with millions of rows and even less once you start doing lots of merges and lookups etc.  (There are optimization options for these but they require lots and lots of memory to be successful). 

 

My approach usually is to apply only the absolutely necessary transforms in Power Query (avoiding merges/joins wherever possible) and then let the Vertipaq engine and the data model do the dirty work.  That will be much faster as it's all in memory already.

 

Can you do a proof of concept? 

View solution in original post

1 REPLY 1
lbendlin
Super User
Super User

Depends.  Power Query is a very powerful language, and it can do a lot of nifty ETL things. But it's not comparable with SSIS or Informatica etc. You will run into performance issues when dealing with millions of rows and even less once you start doing lots of merges and lookups etc.  (There are optimization options for these but they require lots and lots of memory to be successful). 

 

My approach usually is to apply only the absolutely necessary transforms in Power Query (avoiding merges/joins wherever possible) and then let the Vertipaq engine and the data model do the dirty work.  That will be much faster as it's all in memory already.

 

Can you do a proof of concept? 

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors