Data Gateway Timeout on data refresh MySQL

dpombal,

Desktop would refresh successfully because the client has more resource to run the dataset and does not depend on the DataMovement.Pipeline.Gateway to render results.

With that said in the DataMovement.Pipeline.Gateway config file you can edit this settings to your desire value to see if this resolves you problem. 

</setting>

<setting name="DbConnectionPoolMaxSize" serializeAs="String">
<value>256</value>
</setting>

This are the options available for increasing or decreasing calls to the DB, so you can find the corresponding settings in the same file and play with them to see which one help you resolve the timeout.
* DbConnectionPoolMinSize: minimum size of the DB connection pool.
* DbConnectionPoolMaxSize: maximum size of the DB connection pool.
* DbConnectionPoolProactiveCreationCount: number of pro-actively created connections for a DB connection string.
* DbConnectionPoolExpirationTimeout: maximum time a connection can stay in the pool without being used.

Thanks,

Conarl_On_BI