Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
In our company, before Power BI existed, a SSAS cube was built (getting data from SQL server ) for analysis purpose. And then there were a number of Power BI dashboards built on top of the SSAS (data model in SSAS) and a number of Pbi dashboards built on top of SQL server (data model in pbi).
Our data set was not that big, I doubt it would ever exceed 1 million rows. We are dealing with probably 10 thousands rows regularly. I am new to SSAS. I wonder if there is a point using Cube and build dashboards over it instead of direct pull data and build model in Power BI? It seems there are so much overlap between these two.
Now we are considering to move all the dashboards (and create new ones) to one single data source, either SQL server or SSAS. Which one makes more sense? I am leaning towards SQL server -> Power BI directly, but I am new to SSAS. Any suggestion is appreciated.
Thanks.
Solved! Go to Solution.
@Anonymous Given such a small dataset, I would go with SQL Server and Power BI route and remove SSAS completely. To discuss it further, you can reach out to me directly via email (it is in my signature) and we can go over the pros and cons of both solutions.
Good luck!
Check my latest blog post Compare Budgeted Scenarios vs. Actuals I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos to whoever helped to solve your problem. It is a token of appreciation!
⚡Visit us at https://perytus.com, your one-stop-shop for Power BI-related projects/training/consultancy.⚡
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
@Anonymous Given such a small dataset, I would go with SQL Server and Power BI route and remove SSAS completely. To discuss it further, you can reach out to me directly via email (it is in my signature) and we can go over the pros and cons of both solutions.
Good luck!
Check my latest blog post Compare Budgeted Scenarios vs. Actuals I would ❤ Kudos if my solution helped. 👉 If you can spend time posting the question, you can also make efforts to give Kudos to whoever helped to solve your problem. It is a token of appreciation!
⚡Visit us at https://perytus.com, your one-stop-shop for Power BI-related projects/training/consultancy.⚡
Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!
Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo
If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤
Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 44 | |
| 42 | |
| 19 | |
| 19 |
| User | Count |
|---|---|
| 74 | |
| 71 | |
| 34 | |
| 33 | |
| 31 |