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.
I am trying to create a DataFlow for a 2.6GB fact table and I am getting this error:
This is on a P3 node, so you would think that the capacity is not an issue. Any ideas? Can a diagnose this myself or do I need the PBI Admin?
Thanks!
Solved! Go to Solution.
Strangely, putting in an explicit "SELECT *" SQL source query worked instead of choosing the view object from the PowerQuery interface. Don't know why, but it fixed my issue.
Side question. We are trying to reduce load on the DW by creating base Data Flows that other workspaces can base their own Data Flows off of. This should limit every single dataset from query redundant data from the DW. It also puts the files in ADLS which opens the data up for other uses-cases like ML or Databricks.
I am trying to connect my dashboard to fetch data connected to kobotool box. It was happening earlier but now says stack overflow while the web address is same.
You will want to do performance comparisons. I don't think dataflows will gain you anything in that particular scenario.
Strangely, putting in an explicit "SELECT *" SQL source query worked instead of choosing the view object from the PowerQuery interface. Don't know why, but it fixed my issue.
Side question. We are trying to reduce load on the DW by creating base Data Flows that other workspaces can base their own Data Flows off of. This should limit every single dataset from query redundant data from the DW. It also puts the files in ADLS which opens the data up for other uses-cases like ML or Databricks.
can you try with a different table from that same Azure SQL database?
Side question - Why do you want to stuff data that is already in Azure into yet another Azure data storage (dataflows)?
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.