We have experienced cases of SQLYog hanging when trying to terminate the application. This is because when the InfoTab is activated as it is being closed, SqlYog performs a ‘SHOW TABLES WHERE ENGINE IS NOT NULL’ that can take a significant amount of time for our bigger DB’s. The latest version of SQLYog (v9.5) has removed the check box allowing users to disable the auto-open of the ‘InfoTab’. This option was available in v9.3 and earlier versions of sqlyog.
One of our programmers discovered this issue and has discovered a ‘work-around’ for this issue:
In the file: %APPDATA%sqlyogsqlyog.ini
There is an ‘InfoTabOpen=x’ option per-connection where x is 1 or 0.
Either adding/setting this option to 0 will keep the InfoTab from auto-opening as new DB connections are established.
Is this supposed to be a normal occurring issue? We have used this workaround on all of our computers because it has the possibility to swamp our servers due to the quantity of their tables.
With this Option turned on, there is no delay in closing any Query tabs or Connection tabs, as well as no issues with the application becoming unresponsive.
This was discovered while comparing 9.3 options to 9.5 as well as the .ini files. We are currently using 9.3, and 9.5+ Enterprise versions.
