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

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
analyticsyc
Frequent Visitor

Best Practices for Sustainable Data Transformations

I work with Syspro (an ERP system) which sits on top of an SQL Database. It records all of our company's sales information, and I use PowerBI to tie together multiple tables and create reports for different departments. I currently have 1 main model, which I adjust visuals for different end users. As the number of reports has grown, I am struggling to keep changes consistent throughout all my models. I make my data transformations in Power Query, which is great, until I need to make the same change across 10+ different files. 

 

I'm hoping someone has advice on how to create a sustainable method of data transformations rather than using Power Query. My initial thought was using SQL to transform my data, and then linking all my models to that transformed data. I would store the transformed data in Azure. That way, when I need to make a change (say adding a calculated column), I only have to make the change in SQL and all my PowerBI files are automatically updated the next time they refresh. One requirement is that wherever this transformed data is stored, I need to be able to schedule refreshes through power automate. Using SQL is just my initial idea though, and I'm interested in hearing other's opinions on what works best.

1 REPLY 1
lbendlin
Super User
Super User

Read about data warehouse, data lake and (the newest fad) data lake house.  

 

Microsoft offer Dataflows if you want to apply your transforms once.  They are also pushing datamarts which are a very tortured way of giving direct query access to dataflows.

 

If your number of data domains is small and you think you can do the modeling then keeping everything in SQL server is not out of the question.  For larger endeavors look into Purview or Collibra.

 

Don't forget the oldie but goldie - SSAS.  That could provide you a multi dimensional data model that might work for your needs.

 

And lastly think about auditing and recoverability.  Think very hard about these.  It's "easy" to create a reusable data model but it is very very hard to keep it sane.

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

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

Top Solution Authors