Home/ Questions/Q 382285
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T15:10:03+00:00

I have an application that holds data referencing 300,000 customers. When a user did

  • 0

I have an application that holds data referencing 300,000 customers. When a user did a search the result was often bigger than our MaxRequestlength would allow, we have dealt with this in two ways: We have increased our MaxRequestLength to 102400 (KB) and required the user to supply two letters of the first Name and two letters of the last name, to limit the sheer # of customer records returned. This keeps us from exceeding the MaxRequestLength limit.

I was just wondering if anyone had any insight in to whether this was a particularly good approach, whether there is a limit to how big MaxRequestLength could be or should be, and what other options might be useful in this situation.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Most web applications I have seen deal with this by returning a paginated list, and displaying only the first page of results.

    In modern implementations using ORM’s, “Skip” and “Take” operators are used to retrieve only those records which are required for a given page.

    So any given request is no longer than the number of records on one page.

    • 0