In Qlik Sense SaaS, I cannot change Query timeout in ODBC connector accessing SQL Server data source

[alexis]

Hi
In Qlik Sense SaaS, I did the following:
a) In ODBC Data Source Administrator I created a 64-bit DSN using SQL Server driver - I called it XYZ

b) The DSN connector works perfectly

c) In Qlik Sense I created a connection using the ODBC connector using the XYZ DSN defined above. My connection string in my application is of the type:
LIB CONNECT TO 'XYZ (cypapp3_alexis)';

d) This also works perfectly

Occasionally my queries to the source time-out and I wish to extend the Query timeout period to give the source the chance to deliver the data and stop my application from crashing. I cannot find ANYWHERE any way of changing the Query timeout period.

CAN SOMEONE HELP??

Regards and thanks in advance

[Kushal_Chawda]

@alexis  see below link if that helps. It seems to be possible but you need to make sure that these commands are supported by the database. It should at least send an error message instead silently exiting query

https://community.qlik.com/t5/App-Development/Qlik-Sense-Timeout-loading-data-from-SQL/m-p/1219181

[alexis]

Hi Kushai and thanks for responding.

The "solution" talks about:
"When you are setting the connection, at the bottom you have some space fields (under the header advanced) where you can fill some settings. We tried the following ones and it worked fine:

There is no "Advanced" section and no space as described. Perhaps this has changed over the years (this answer is 7 years old after all!)..

The only "hope" that I have is on the QMC when I examine the Data connector (see below) there is a line called "Connection String" (see arrow below) that contains the string
ODBC CONNECT TO [ACSCYPRUS;]

Where LIB CONNECT (as used in code) does not allow for any parameters to be added such as "QueryTimeout=123", I have seen elsewhere on the internet people using such a parameter when using 
ODBC CONNECT, so I wonder if I can modify the above to something like:
ODBC CONNECT TO [ACSCYPRUS;QueryTimeout=600]?

[Kushal_Chawda]

@alexis  Note that the "Query Timeout" parameter may not be supported by all ODBC drivers, so it's possible that this solution may not work for your specific driver. If that's the case, you may need to explore other options or consider using a different ODBC driver that supports query timeouts.