Forum Discussion
Azure Cost Management scheduled refresh
Knelly037 if the data is fully imported into PBI tables I would assume no further issues joining them.
But if so then with the limitation of not having access to a capacity or Fabric items the only additional idea I have is storing the data in a dedicated database and load the data from there to Power BI.
Best regards!
thanks Mauro89 appreciate the guidance.
1. Understood
2. I've followed all the steps, incremental refresh set for 7 days, and still get the timeout issue so I'm assuming just looking from outside there shouldn't really be any reason why it shouldn't work if those steps have been put in?
Splitting was something I looked at, e.g. run a manual refresh for historic data and seperate query just for the current month. The current month refreshes fine in isolation but if I then have a append step in desktop to join the two data sets together then I get the same timeout issue (I assume again because of size!?)
Knelly037 if the data is fully imported into PBI tables I would assume no further issues joining them.
But if so then with the limitation of not having access to a capacity or Fabric items the only additional idea I have is storing the data in a dedicated database and load the data from there to Power BI.
Best regards!