Share
Report
6We 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.
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?
Categories:
I have the same question (0)
All responses (
Answers (
