Can we extend the record count function execution time?

Question

I have a few clients working with massive data sets and displaying a lot of data. I have tried splitting the inquiries in two etc, but we are now down to the minimum acceptable amount of data and the system is returning the “failed to get record count” error. My understanding is that the system gets 2 or 3 seconds to get this record count. Can we extend this timer?

I need a scalable solution for these companies as they continue to grow (one of them is an acquistion company and they are very agressive in their growth). I’d love to double the time to give them some breathing room.

THANK YOU!

icon

Best answer by VladS 12 October 2023, 18:50

View original

VladS · Accepted Answer

Hello @Michael Hansen !To my knowledge, the default value for a Report and Query Timeout is 30 seconds. You can adjust these values by navigating to the web.config file, and adjusting the reportQueryTimeout + queryTimeout values respectively. Let me know if increasing those values helps out with this issue your team is facing. Thanks!

manikantad18 · Answer

Hi @Michael HansenHow many records you will get in the GI?As @Naveen Bogamentioned we can see 10million records in GI,Generally the error comes because of Incoorect GI relationsOne way to optimize a Primary List is by reducing the number of fields that have "Use in quick search" enabled (highlighted)Check the tables in the GI, if there are any that are not necessary we recommend removing them (obsolete tables)TO=o calculate the count and display the results, the system needs to run two queries. To ensure the responsiveness of the application, the Generic Inquiry system will wait for a predetermined amount of time (a few seconds). If the count of records is not returned in the allotted time, the query is canceled and the GI will only display the records.More than likely, this means that the GI has a complex join expression or condition that requires full table scans instead of faster-clustered index operations. 'Analysis of the SQL Query Execution plan through SQL Management Studio is recommended in such cases. In some cases, it can simply be because you’re missing a field in the relationship (ex: joining by OrderNbr instead of OrderType, OrderNbr).One way to optimize a Primary List is by reducing the number of fields that have "Use in quick search" enabledCheck the tables in the GI, if there are any that are not necessary we recommend removing them (obsolete tables)Another suggestion would be to enter a value for the "export top" field if the client is not exporting all the values and the first few only

Can we extend the record count function execution time?

3 replies

Reply

Reply

Sign up

Social Login

Login to the community

Social Login

Scanning file for viruses.

This file cannot be downloaded