none
Guidance on setting the AggregateQueryLimit Deployment Property on the CONFIG db

    Question

  • The default value for AggregateQueryLimit on a CRM installation is 50,000
    A lot of people have hit the "Aggregate Query limit exceeded" when performing aggregate operations such as COUNT using fetchxml when the entity being queried has more than 50K records for performing an aggregate operation using the SDK(from an external app) and/or using CRM graphs
    I have seen solutions ranging from updating the DeploymentProperties table to using the UpdateAdvancedSettingsRequest to up this number.
    What I haven't seen anybody talk about is real world performance impact (if any) caused by this change.
    Can anyone from the Product team and/or anyone who has upped this setting in a real world enterprise grade production deployment comment on the ramifications of increasing the value of this setting to say 100,000,000

    -Abhijeet

    Tuesday, June 11, 2013 2:42 AM

All replies