[Jim Harris]

Is there a brave soul out there who has played around with these two dex.ini settings – SQLCursorBlockSize and SQLQueryTimeout? 
From Leslie Vail’s excellent collections of dex.ini switches https://dynamicsconfessions.blogspot.com/2014/02/dexini-switches-my-complete-list.html
these are defined as:

SQLCursorBlockSize=100 Removing this setting

To prevent the Loop stopping at 25 records when looping through a range of records with Dexterity.

SQLQueryTimeout=0

Including this setting in your DEX.INI file will control the period of time Dexterity will wait for a SQL query to execute. When set to 0 it will wait indefinitely. A valid range of values for this setting are 0 to 9999. If this setting is not included, the default value is 300 seconds.

I’m curious what the practical impacts are with both of these. 
Could increasing the cursor block size improve performance in an environment with high POP, PM, SOP and AR transaction volumes?  
Does the query timeout setting come into play on inquiry windows in GP?  If not there, then where?

——————————
Jim Harris
Director of Information Systems
ExamWorks, Inc.
Atlanta GA
——————————