Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
With DES being EOL/EOS in November, has anyone discovered other options for getting CRM data out to an SQL (Azure or otherwise) server?
We have some data that is populated in CRM custom entities/forms etc, that is presently fed into an AzSQL instance for processing by another application. With Azure Data Synapse being the replacement, it only allows for processing of the data and it has to be in Azure Data Lakes Gen2, which also has no direct way of writing/synching with Azure SQL.
I think many of us are looking at this.
For some people, the replicated data in the Synapse Workspace is good enough.
It is a "Serverless SQL Pool" , which you can query like a SQL instance.
The structure of the data in those tables look more or less identical to the tables you currently get from DES.
It all depends on how you are using the data for your other application.
The Synapse Serverless Pool isn't that quick. It is absolutely fine if you are just going to be running reports against the data. A few extra seconds will be ok.
If you are going to be hitting the data a lot, it just won't be responsive enough.
At this point, you'll probably have to look at a Synapse Pipeline (Azure Data Factory) job to push the data from Synapse to your SQL database.
So, you can build a pipeline job to ship the data out to Azure SQL from Synapse/Azure Data Lake.
So, unfortunately it is not as simple as DES was to use.
I personally wouldn't have minded if they had just said "we want to charge for DES".
It would have been less painful than all this.
I have been on this thread too. Where others have also used pipelines to get the data out to Azure SQL.
Business Applications communities