Improve FetchXML request performance


Unsure about entity vs. table? See Developers: Understand terminology in Microsoft Dataverse.

You can use the LateMaterialize option in FetchXML requests to break up such requests into smaller, more usable segments, which can improve the performance of long-running FetchXML requests.


Performance improvements depend on the data distribution for each participating table and linked table. Late materialization might not always provide a performance benefit. It's best used if you're experiencing performance issues with your existing fetch request.

Executing a traditional fetch for a given number of the top table records will pull all the columns in the select list that meet the filter criteria. Let's say you're pulling the top 500 records on a table that has 100 columns and 100,000 rows that meet the filter criteria. This request can cause issues in two ways:

  • The 99,500 rows will pull all columns, even though you only need to populate the select list for 500 rows when returning to the client.

  • The query optimizer can generate an arbitrary order when retrieving the child columns, resulting in a data order you don't want.

When you use LateMaterialize, you create a fetch that will:

  • First pull only the primary ID of the top number of records specified.

  • Select only the columns of data needed based on the primary IDs that were retrieved—for example, where only five columns are needed for display in the form.

By pulling only the needed data after the primary IDs are collected, the retrieval is much faster because data that's not needed for the current operation is excluded.

This is most beneficial when:

  • The table you're querying has one or more links to other tables for column data.

  • The table contains many columns.

  • The table contains logical columns.


<fetch version="1.0" output-format="xml-platform" latematerialize="true"
 mapping="logical" distinct="true">

  <entity name="[entity]">​
    <attribute name="[attribute]" />
    <link-entity name="[entity]" from="[linked entity]" to="[linked entityid]"
                 link-type="outer" alias="[alias]">​
      <attribute name="[name of linked entity column]" />​
    <filter type=[filter type]>​
      <condition attribute="[column]" operator="[operator]" value="[value]"/> ​


<fetch version="1.0" output-format="xml-platform" latematerialize="true"
       mapping="logical" distinct="true">

  <entity name="account">​
    <attribute name="accountnumber" />​
    <attribute name="createdby" />​
    <attribute name="ownerid" />​

    <link-entity name="account" from="accountid" to="parentaccountid"
                 link-type="outer" alias="oaccount">​
      <attribute name="createdby" />
      <link-entity name="account" from="accountid" to="accountid" link-type="outer"
        <attribute name="createdby" />​
        <attribute name="accountid" />​
        <attribute name="name" />​

    <link-entity name="account" from="accountid" to="accountid" link-type="outer"
    <filter type='and'>​
      <condition attribute="statecode" operator="eq" value="2"/> ​


FetchXML support for query hints

Microsoft SQL Server supports a number of query hints to optimize queries. The FetchXML language supports query hints and can pass these query options to SQL Server.


The query hints feature is recommended to be used only by developers who fully understand how FetchXML is translated to SQL. This is to ensure that developers using this feature avoid inadvertent performance regression.


<fetch version='1.0' aggregate='true' output-format='xml - platform'
mapping='logical' options='OptimizeForUnknown,DisableRowGoal,Recompile'>

  <entity name='account'>

    <attribute name='accountid' aggregate='countcolumn' alias='countAll'/>
    <filter type='and'>
      <condition attribute='statecode' operator='eq' value='0' />

    <filter type='or'>
      <condition attribute='name' operator='like' value='%Test%' />
      <condition attribute='accountnumber' operator='like' value='%Test%' />
      <condition attribute='emailaddress1' operator='like' value='%Test%' />
      <condition attribute='telephone1' operator='like' value='%Test%' />


Supported query options

The supported FetchXML query hints are listed in the following table. The table also shows the translation of FetchXML query hints into SQL Server query hints.

FetchXML hint SQL Server hint
OptimizeForUnknown Optimize for unknown
ForceOrder Force Order
Recompile recompile
LoopJoin Loop Join
MergeJoin Merge Join
HashJoin Hash Join

See also

Use FetchXML to construct a query
Hints (Transact-SQL) - Query