
Announcements
We are heavily reliant on the DES as it exists today and have been monitoring developments for the Synapse Link over the past year since the DES deprecation announcement. To date, we have not found a comprehensive guide on how to leverage the Synapse link and pipelines to exactly replicate the capabilities of DES – a service that results in a SQL Server database (serverless / dedicated pools are not sufficiently performant by comparison) that is up to 15 min delayed replication of the dataverse entities configured for export, including the OptionsetMetadata entities. We have considered and tested all of the approaches we can find through the following links but NONE are a true replacements for the DES:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-incremental-updates
Is Synapse Link for Dataverse even capable of replacing Data Export Service. Is there some secret sauce I'm missing here? Microsoft docs seem to only offer limited use cases / preview functionality and not focus on what would be a like-for-like replacement of the existing service.
Hi @crossbox,
Yes, Azure Synapse Link (ASL) is the "replacement" of DES as per Microsoft, but your obversation is correct that it's not a one-to-one technical replacement, and I feel your dissapointment that there's not a "true" replacement. Microsoft suggests that it is the replacement because the same "business" outcomes can be achieve by ASL, that is, replicate data (including on-premise), enable Dataverse data for BI, digest and intake within the enterprise/organisation, etc.
If you need the data in SQL Server, you'll need to implement an additional process (possibly with Azure Data Factory or Synapse Analytics) to import the data from DataLake. More info: https://learn.microsoft.com/azure/data-factory/connector-sql-server?WT.mc_id=DX-MVP-5004271
Hope this clarifies...