Wny Sqlyog Canot Handle Database With Over 500 Table

[micsqlyog]

Hi,

i'm using the sqlyog 5.18 community edition, recently i use it to manage my archive database in which contain more then 1000 tables. However, when i select my database from the left side menu, the sqlyog just jam there for a long long time sometime is dead and sometime even success, it just list out partial of those table and then from that moment the sqlyog going crazy in the sense that all db that i select it just display partial of those tables. The only way to fix it is close down the sqlyog and then to restart the mysql.

Is there any solution for this one??

Thanks

[peterlaursen]

This is a known issue with the MySQL Server and not SQLyog.

(queries to `Information_schema` are slow – try searching [url=”http://bugs.mysql.com!!))”]http://bugs.mysql.com!!))[/url]

MySQL claims that this is fixed (at least the bug reports are closed).  

You should upgrade the server version to 5.0.27/28 or 5.1.14.

(Also you should upgrade SQLyog .. but for other reasons!)

[micsqlyog]

peterlaursen wrote on Dec 21 2006, 09:07 AM:

This is a known issue with the MySQL Server and not SQLyog.

(queries to `Information_schema` are slow – try searching [url=”http://bugs.mysql.com!!))”]http://bugs.mysql.com!!))[/url]

MySQL claims that this is fixed (at least the bug reports are closed).  

You should upgrade the server version to 5.0.27/28 or 5.1.14.

(Also you should upgrade SQLyog .. but for other reasons!)

ok thanks man 😀

[micsqlyog]

peterlaursen wrote on Dec 21 2006, 09:07 AM:

This is a known issue with the MySQL Server and not SQLyog.

(queries to `Information_schema` are slow – try searching [url=”http://bugs.mysql.com!!))”]http://bugs.mysql.com!!))[/url]

MySQL claims that this is fixed (at least the bug reports are closed).  

You should upgrade the server version to 5.0.27/28 or 5.1.14.

(Also you should upgrade SQLyog .. but for other reasons!)

ok thanks man will try it 😀

[peterlaursen]

However ..

we are not impressed with this 'solution' my MySQL AB.    🙁

Queries to Information_Schema is still slow compared to “SHOW …” and “SHOW … STATUS … ” statements.  From version 5.22 RC1 we will try to avoid querying Information_Schema whenever possible.  We think that it is possible everywhere except when clicking the + sign left to the 'triggers' folder in Object Browser (there is a privilege issue here as it takes the SUPER privilege to “SHOW TRIGGER STATUS ..”).

[Author]

Posts