[peterlaursen]

Well ..

We SET NAMES UTF8. But it fails after some point.

I will not guess more now. We will need to check in a similar environment..

[peterlaursen]

ok .. we will check.

But please tell: if you try multiple times does this happen always and at exactly the same row?

[peterlaursen]

What is the SQLyog version and the MySQL server version you are using?

[peterlaursen]

There is no screenshot! First you will need to upload and next to attach it.

[peterlaursen]

OK .. please read release notes for version 6.06 (from here http://faq.webyog.com/content/33/7/en/sqlyog-version-history.html for instance)

“Files used by SQLyog that are not read-only (.ini, .log, .err) are now no longer created in 'program files' files tree (or what localized name it has). The storage follows Microsoft recommendations for the various Windows versions.”

If you are using Vista or a higher version of Windows and has UAC ('user account control) turned on (what is default), such old SQLyog version as you are using is not compatible what will explain what you are telling. It was released 6 years ago and when we released it we (obviously) could not know what changes would happen to Windows in the future.

The solution is to upgrade SQLyog. The version you are using also does not support unicode. We don't support such old versions at all. But if you turn off UAC (from Control Panel .. User Accounts) it should still work as expected.

[peterlaursen]

What is the SQLyog version you are using?

And what is the exact details of the MySQL server?

What is the error log you are referring to? The MySQL error log? This is maintained by the server and client configuration has absolutely nothing to do with it.

I have no issue running SQLyog as Administrator in Win7. I simply do not understand how “running SQLyog as Administrator” is Windows can have anything to do with authentication to MySQL.

[peterlaursen]

I am afraid we forgot to update here.

Please refer 11.1 Release notes:

“Changes in the order of execution of statements when opening a new connection. Now the user specified init-command(s) will be executed after SQLyog's init-command(s).”

.. so now you are able to use the INIT_COMMAND

[peterlaursen]

There is an option in the Dashboard page itself to “Plot on values per second”. If you check this, what is displayed is the average pr second (calculated simply like: the increase of the status variable's value between two samples / seconds between two samples).

Please see attached image

[attachment=1907:persecond.jpg]

MONyog exectues “SHOW GLOBAL STATUS” with the sample interval defined. MONyog can only know what information it retrieves from the server. So if you want the true value for every second displayed you will ahve to set the sample interval to 1 second. And actually this will not be perfectly true, because what happens is that after receiving a result from the server, MONyog will wait 1 second and send the query again. So what you get is actually the setting + network latency + MySQL response time. With a remote server the network latency can be several seconds (if MONyog and MySQL is on same machine the latency is mostly neglible). We also do not recommend that low setting (in production even though we use it ourself for stress-testing) as it will generate a lot if I/O (the more, the more MySQL servers registered) on the machine where MONyog runs (traffic to and from MONyog's embedded database) and the embeded database will occupy a lot of diskspace (depending on retention interval setting of course).

[peterlaursen]

You have this option it the context menu for a table or by using Ctrl+F11 keyboard shortcut (first select the table in Object Browser).

Please see this image:

[attachment=1906:newtab.jpg]

From release notes (here http://faq.webyog.co…on-history.html for instance):

Version 10.0: “Added an option to open a DATA tab in ‘sticky’/persistent mode. A DATA tab opened like this will remain open until closed manually by user. If a DATA tab is opened in ‘non-sticky’/non-persistent mode it will be replaced when opening another table in ‘non-sticky’/non-persistent mode.”

Version 10.1 :”It is now optional whether DATA, INFO and HISTORY tabs shall display in ‘upper pane’ (as in 10.0) or in ‘lower pane’ (as before 10.0). The setting is available in tools .. preferences .. general. Note that for DATA tab this applies to the ‘non-sticky’/non-persistent DATA tab. A ‘sticky’/persistent DATA tab will always display in ‘upper pane’.”

[peterlaursen]

No .. a client cannot do this. You will have to restart the server with appropriate options waht will require elevated priviles to the OS and file system. And maybe even you will need to recompile the server (if it was compiled without InnoD:cool: or install another server.

[peterlaursen]

There is no way to bypass this problem currently.

[peterlaursen]

Well .. it is 11.21 beta1 that has been released. We expect to release 11.21 GA today itself.

[peterlaursen]

What privileges does the user have?

Please execute “SHOW GRANTS;” on both servers as the same user you use for Schema Sync, and paste the result here.

[peterlaursen]

What MySQL version is that online server (“SELECT VERSION();”) and what are your privileges to that server (“SHOW GRANTS;”)?

This looks like some cheap 'hsared hosting' and I doubt you will have privileges enough (even if it is possible to load InnoDB as a plugin at runtime).

Your headline reads “Sqlyog Sync With Different Storage Engines”. Could you elaborate that? Is it the problem that Schema Sync wnats to change tables on teh server to InnoDB, because they are on the ? In that case we already have this request here: http://code.google.com/p/sqlyog/issues/detail?id=847

But a server with no InnoDB support can at best be characterized as a 'historical relict' nowadays IMO.

[peterlaursen]

Please tell: what are your MySQL server versions (source and target)? And what is your SQLyog version?

[Author]

Posts