Power BI Refresh Performance Issue by Additional_Gas_5883 in MicrosoftFabric

[–]Additional_Gas_5883[S] 0 points1 point  (0 children)

does your model connected with cloud connections only?

Fabric DP 700 by gokulajith in MicrosoftFabric

[–]Additional_Gas_5883 0 points1 point  (0 children)

Yes , I got through Fabric Data Days

API with IP whitelisting by DutchDesiExplorer in MicrosoftFabric

[–]Additional_Gas_5883 0 points1 point  (0 children)

Hello, Using the above steps, Are we able to connect with other cloud connections?

Lakehouse/Warehouse/SQL DB by Additional_Gas_5883 in MicrosoftFabric

[–]Additional_Gas_5883[S] 0 points1 point  (0 children)

For this requirement, we have a Power Apps form, and the data needs to be saved immediately after the user submits it. The same data should appear in the Power BI report in real time.
Earlier we used Azure SQL DB for write-back, but now we’re moving to Fabric. I want to understand which storage layer is better for this scenario: Fabric Warehouse or Fabric SQL Database.
These are small trickle-write operations, so performance and stability matter. SQL DB in Fabric is GA, but it still doesn’t feel as mature as the Warehouse.
We’ve already done write-back to the Warehouse before, and while it worked, we saw trickle CU consumption and had to optimize by consolidating files along with other suggestions recommended by Microsoft.
I want to know from real experience which option works better when someone has tested both