We were able to identify the issue was related to the database server. The problem was that the database server was scheduled to open a secure VPN connection to other data sources for ETL processes and everytime that happened, the QVS connection got disconnected. When we restarted the DSC on QVS, then everything worked fine again.
Working on setting up the scheduled service restart and believe that this should resolve the issue for now. Still not sure why QVS cannot do this automatically for DSC when all other applications including QV reloads work fine.
I don't know the architecture, but i think the DSC keeps the connection between it and the Database alive.
This connection is only "refreshed" if it is restarted or if you click the apply button...
BTW, you might also notice that the web server also crashes (if you are using the Qlikview Web Server), because the DSC becomes irresponsive to any web server requests.
Qlikview Senior Consultant
Where do you find the "Enable Query Timeout"?
It is not the Query time out that is the problem. The problem is that the connection gets closed after a while. I think it is due to inactivity but I'm not sure on that.
In the connection pop-up in QMC I just specify the driver, schema and table that shall be used and QV builds the connection string.
This is the info typed in.
Cache expiry in minutes
Conn db name
Data source name
MySQL ODBC 5.2w Driver
Entity table db name
Groups table db name
Override connection string
Nothing if just info above shall be used
Service timeout in seconds
Maybe I the solution is to define an overriding connection string?
I found that there is a KeepAlive flag I can pass in the string to the MySQL DB. Haven't tested it yet though
The KeepAlive defines the time between keepAlive-packets are sent according to www.connectionsstring.com
I think Marcus is talking about settings in the 'ODBC Data Source Administrator' but in my world these settings are not related to the 'Configurable ODBC' since no one of these connections are used. You build up you connectionstring in the form getting prompted when editing the 'Configurable ODBC'.
The connection on my server has been alive now for three days (all-time high) since I created a task that reloads every hour and distributes to users found in the 'Configurable ODBC'.