We are integrating Azure service into our Dynamics 365 project. As part of this, we need to create logs to track multiple records generated by the Azure service. The number of records could vary greatly depending on the volume of usage.
To handle this, we are considering using an Elastic Table in Dataverse since it seems suited for scenarios with high data volume and unpredictable growth. However, we are also wondering if a Standard Table might suffice for our needs.
Key considerations:
Data volume can grow significantly over time.
Need for efficient querying and performance at scale.
Can anyone share their experience or recommend the best approach for such a use case? Are there any pitfalls with Elastic Tables in Dynamics 365 that we should watch out for?
I am not completely sure I understand. The data sounds like it should go in the Data Lake, not in Dataverse at all, its going to consume a ton of data and its transactional. Are you sure you really want that? I always make sure people understand the ramifications. It's not just can it expand enough, it's the impact on the system putting them in, and then what do you plan to do with them. Run Queries?
Cosmo DB, Spark, Data lake etc etc seems like more of what you need and then if you need analytics point Power BI at that, because getting that data back out using Dataflows etc EEEWWWWW nope.. nope.
Just something to really think about.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
6
Share
Report
All responses (
Answers (
