13
When a filter is added to a query object in SQL, the generated SQL behind the scenes will wrap the field being tested in an ISNULL.
The problem with this is it prevents use of any indexes, which in turn means that it will cause a full table scan.
This reduces the usefulness of queries on larger tables, as the performance is lower than it needs to be.
The suggestion would be to stop using ISNULL in the generated SQL.
"Is it good now" would then be validation in the query plan that indexes are in fact being used.
The problem with this is it prevents use of any indexes, which in turn means that it will cause a full table scan.
This reduces the usefulness of queries on larger tables, as the performance is lower than it needs to be.
The suggestion would be to stop using ISNULL in the generated SQL.
"Is it good now" would then be validation in the query plan that indexes are in fact being used.
STATUS DETAILS
Needs Votes
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team