Bug #99712 server variable max_execution_time now set in ODBC driver
Submitted: 27 May 19:19
Reporter: Alex Miller Email Updates:
Status: Open Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:5.3.14 OS:Microsoft Windows
Assigned to: CPU Architecture:Any
Tags: ODBC

[27 May 19:19] Alex Miller
Description:
On previous versions of MySQL ODBC driver (5.3.4 for example) there was no max_execution_time value set for session or global when connecting to a MYSQL linked server in MSSQL

Select * from openquery(linkserver, 'select @@max_execution_time, @@global.max_execution_time')

@@max_execution_time	@@global.max_execution_time
0	                0

After updating to the latest ODBC drivers 5.3.14, there's a value set for both

Select * from openquery(linkserver, 'select @@max_execution_time, @@global.max_execution_time')

@@max_execution_time	@@global.max_execution_time
600000	                7200000

MySQL @@version
5.7.29-enterprise-commercial-advanced-log

How to repeat:
Under 5.3.4

Select * from openquery(linkserver, 'select @@max_execution_time, @@global.max_execution_time')

@@max_execution_time	@@global.max_execution_time
0	                0

updated to 5.3.14

Select * from openquery(linkserver, 'select @@max_execution_time, @@global.max_execution_time')

@@max_execution_time	@@global.max_execution_time
600000	                7200000