Share
Report
8Hi Community,
We are currently using recurring Data Export from D365 Finance & Operations to Azure SQL Managed Instance for data synchronization.
The export jobs are scheduled approximately every 30 minutes to control the load on the F&O environment. However, because the synchronization is batch-based, hundreds or thousands of changed records can accumulate in individual tables between synchronization cycles.
We are therefore evaluating Data Events as a way to move from:
D365 F&O → Recurring Data Export (every ~30 minutes) → Azure SQL Managed Instance
to a more incremental and near-real-time approach such as:
D365 F&O → Data Events → MessageBroker (RabbitMQ, etc) → Azure SQL Managed Instance
One of the main motivations for moving away from recurring Data Export is to reduce the performance impact of processing relatively large batches in F&O.
However, Microsoft documentation states that Data Events currently support a burst rate of 5,000 events per five-minute period and up to 50,000 events per hour across all entities for the environment. It also mentions that workloads above these thresholds may experience performance degradation.
This raises a concern for hundreds to thousands data synchronization scenarios.
If multiple entities each generate hundreds or thousands of create/update/delete changes within a short period, the total number of Data Events could potentially reach or exceed these benchmarks quite quickly.
Could you please clarify:
- From an F&O resource and performance perspective, is continuously processing changes through Data Events generally more efficient than processing the same changes through recurring Data Export to Azure SQL Managed Instance?
- If the objective of replacing the 30-minute Data Export is to reduce the performance impact on F&O while also achieving near-real-time synchronization, are Data Events still recommended for entities with relatively high change volumes?
- Is the 5,000 events per five minutes / 50,000 events per hour benchmark shared across all enabled TABLES in the F&O environment?
- If multiple entities collectively generate more than this volume, could Data Events introduce a similar or even greater performance impact compared with the existing recurring Data Export approach?
- For a requirement involving high-volume, near-real-time incremental synchronization from D365 F&O to Azure SQL Managed Instance, what is the Microsoft-recommended architecture?
We are trying to understand whether moving from recurring Data Export to Data Events actually solves the F&O performance concern
Thank you.
All responses (
Answers (
