This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
I am looking into Power BI as a solution for about 400 users. One of my goals is to have a lot of dashboard publishers and PBI is great at that vs Tableau due to cost, strong data management capabilities, Excel integration.
Where I am struggling though is the idea of doing data management within PBI and as a consequence, not pushing for a data lake strategy where all data is loaded in 1 database.
Currently my team compiles data from various data sources, blends it, cleans it, transforms it, using Alteryx and in the future Python. After compilation the data is loaded in Exasol. Then both Tableau or PBI can connect to Exasol and people can build visualizations as they like.
We are not a warehouse, all data is managed by business users, but it is done in 1 place and it is done in a very automated fashion.
Question is, are we moving away from data lake strategies with PBI? If yes, how do you plan to manage this from becoming a spreadsheet nightmare all over again (since there is no control on data)? Also, if yes, will PBI be able to refresh joins and transformations on a scheduled basis?
Those are some of the advantages I am after with the data lake:
On Power BI Service, you can configure Schedule Refresh for your created on-premise Exasol dataset. The refresh frequency can be up to Daily.
Regards,
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 31 | |
| 23 | |
| 23 | |
| 19 | |
| 16 |
| User | Count |
|---|---|
| 63 | |
| 36 | |
| 29 | |
| 24 | |
| 22 |