(mysql.info.gz) performance

Info Catalog

(mysql.info.gz) MyODBC-Net

(mysql.info.gz) Functionality

 
 23.1.14.7 Why Does MyODBC Perform Poorly, and Also Make a Lot of Disk Activity for Relatively Small Queries?
 ............................................................................................................
 
 MyODBC is a lot faster than any other ODBC driver. Slowness might be
 due to not using the following options.
 
    * The *ODBC Tracing* option is turned on. You can cross-check whether
      this option is not turned on by following the instructions from
      here
      (http://support.microsoft.com/default.aspx?scid=kb;EN-US;268591).
 
      [image src="Images/mydsn-trace.png" text=""]
      As shown in the above image, the 'When to trace' option from the
      ODBC Data Source Administrator 'Tracing' tab should always point
      to 'Start Tracing Now', instead of 'Stop Tracing Now'.
 
    * The *Debug version* of the driver is used. If you are using the
      debug version of the driver DLL, it can also relatively slow down
      the query processing time. You can cross-check whether you are
      using the debug or release version of the DLL from the 'Comments'
      section of the driver DLL properties (from the system directory,
      right click on the driver DLL and click on properties) as shown
      below:
 
      [image src="Images/mydll-properties.png" text=""]
    * The *Driver trace and query logs* are enabled. Even if you intent
      to use the debug version of the driver (you should always use the
      release version in the production environment), make sure the
      driver trace and query log options(OPTION=4,524288 respectively)
      are not enabled as shown below:
 
      [image src="Images/mydsn-options.png" text=""]
 

Info Catalog

(mysql.info.gz) MyODBC-Net

(mysql.info.gz) Functionality