In order to use computed column as a range to the entity. Then it's either i put the range on the data project OR i create a view with this computed column method, then add this view to the entity in order to be able to filter on that range. My question is, is one of the approaches better than the other in terms of performance? I mean does it matter if i filter on the data project or in the entity itself?
Initially, I think the second option should be faster, like your expectation, but query plans sometimes can behave like a diva.
To monitor the performance, you can go to the execution history details. There is a start time and end time available. The difference is the duration time.
As Andre said, monitoring your system using performance tools will let you know more specifically which approach is better. Here are some tools and suggestions about performance monitoring, you can refer to them: Performance timer - Finance & Operations | Dynamics 365 | Microsoft Learn: This article provides an overview of the Performance timer, which is a tool that helps you to determine why your system's performance might be slow. Work with performance and monitoring tools in finance and operations apps - Training | Microsoft Learn: Learn how to use performance tools and Lifecycle Services environment monitoring tools to enhance your validation and testing experience in finance and operations apps.
A range or a view with computed columns might have different outcomes for performance. You only provided the range, not the details of how you created the view. It all depends on how SQL will create the plan for each of the two options. I would suggest doing some performance tests on your environment to be sure which one will perform better.
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.
Share
Report
All responses (
Answers (
294,941
