Dynamics CRM 2011 - Performance Impact of AggregateQueryRecordLimit Change RRS feed

  • Question

  • Our deployment of Dynamics is relatively new, yet is in use and has grown quite significantly. As a result, we have some charts displaying an error in Production, and I believe the reason is addressed in another thread:


    Our record count for the particular filter being used when seeing this error on charts is indeed over the 50,000 limit. My question is why is this limit so low? To be able to use charting on large numbers of records is a large part of what 'Dynamics' is all about. Needless to say, we are considering changing this limit as addressed in the previous thread, to be a larger record limit of say, 500,000.

    Does anyone know the performance impact of such a change? Is there a significant reason other than performance that this relatively low limit exists in the first place?


    Wednesday, June 8, 2011 12:56 PM

All replies

  • Is anyone able to address this question? Has anyone changed this field in the database or fixed the chart display error another way? Is there a performance impact to increase the max number of records charts can display? Thank you for your help.
    Tuesday, June 21, 2011 6:34 PM