Share
Report
32Hi,
This is a general question about Azure Synapse Analytics (ASA) and D365 apps
I am aware that you can use Export to Data Lake from F&O and we in fact use it here and have ASA looking at the ADLS using a serverless pool with a number of created views and joins over those views We have a number of PowerBI's consuming from the ASA endpoint.
All good and definitely better than building in the AOT and deploying to Entity Store IMHO.
You can also use Export to Data Lake (renamed Azure Synapse Link) from Dataverse for example from CE.
I am also aware that scaling up,extensibility,mash ups and the fact that you can use SQL or Spark etc.is great and is what the ASA is for
However.
You can use PowerBI directly over Dataverse and create the relationships in PBI which might be a better solution depending upon complexity, volume future scalability etc.
and for that matter you could use PowerBI directly to the ADLS endpoint and cut out the cost of ASA - again assuming volumes were small and you did not want the ADLS files in SQL formats.
I guess my question is the why use ASA (when it is light reporting) and why MS are really pushing it as you absolutely MUST/Should use this as your data manipulator one stop shop for all data processing etc.
Again I am well aware that Data Factory (lite) is inside Synapse studio and PowerBI can be used inside as a linked server etc.
I am just curious to get some feedback here. If I had a client using three of four tables from Dataverse CE I am not sure that I should be advising them to use Synapse and the extra cost, despite the fact that MS seem to be pushing this as a given.
I'm curious a to whether anyone has a view that might enlighten me a bit more,
Thanks
S
All responses (
Answers (
