[Sibin A S]

Hi Chris,

 

Can you please tell the total number of columns in the table that you have been trying to sync. Also tell us the SQLyog version and MySQL server version.

 

Regards,

Sibin

[Sibin A S]

Hi Larsen,

 

We have added the feature to filter the users based on a string in the drop-down list in the ‘User Manager’ in SQLyog 12.2.5 release which was released just few minutes ago. You may refer the release notes and also find the new features added, from our blog >> http://blog.webyog.com/sqlyog-mysql-gui-12-2-5-released/

 

Regards,

Sibin

[Sibin A S]

Hi,

 

We have fixed this in SQLyog 12.2.5 release which was released just few minutes ago. You may refer the release notes and also find the new features added, from our blog >> http://blog.webyog.com/sqlyog-mysql-gui-12-2-5-released/

 

Regards,

Sibin

[Sibin A S]

Hello,

 

We have added the Foreign key support for MySQL Cluster v7.3 and above in SQLyog 12.2.5 release which was released just few minutes ago. You may refer the release notes and also find the new features added, from our blog >> http://blog.webyog.com/sqlyog-mysql-gui-12-2-5-released/

 

Regards,

Sibin

[Sibin A S]

Hi John,

 

We have added the JSON support in SQLyog 12.2.5 release which was released just few minutes ago. You may refer the release notes and also find the new features added, from our blog >> http://blog.webyog.com/sqlyog-mysql-gui-12-2-5-released/

 

Regards,

Sibin

[Sibin A S]

Hi,

 

Thank you for taking time to report this. We are checking this.

 

Regards,

Sibin

[Sibin A S]

Hi Ferzok,

 

This is because all SQLyog versions before 11.5 did not support ‘Session Restore’ feature and hence you may not find the ‘connrestore_backup.ysav’ file. Session Restore feature was added in SQLyog 11.5. You may refer the release notes, here >> http://blog.webyog.com/sqlyog-mysql-gui-11-5-released/ and the blog on session restore, here >> http://blog.webyog.com/sqlyog-introducing-session-restore/

 

Using the latest version of SQLyog, you can manually save a session savepoint by either using the keyboard shortcut “Ctrl+Shift+S” or from the menu >> “File -> Save Session” before closing SQLyog. This enables you to open the session in future.

 

Regards,

Sibin

[Sibin A S]

Hi Ferzok,

 

When you open SQLyog while a server is not running, which was previously running/connected to. SQLyog would give a connection error and save the backup of the session at “C:Users{user_name}AppDataRoamingSQLyogconnrestore_backup.ysav”. 

 

Please try to open the session ‘connrestore_backup.ysav’ (from the menu “File -> Open Session Savepoint”) where the backup of session was saved, only after ensuring the server is running and you are able to connect to the server. This would ensure that the query tabs for the remote server and the queries in it are restored.

 

 

 

The “connrestore_backup.ysav” file is overwritten when a particular server is down when SQLyog tries to connect to it.

 

Therefore, you may manually save a session savepoint by either using the keyboard shortcut “Ctrl+Shift+S” or from the menu >> “File -> Save Session” before closing SQLyog.

 

The manually saved session can then be opened using the keyboard shortcut “Ctrl+Shift+O” or from the menu >> “File -> Open Session Savepoint”.

 

You can find the information for the same in our doc, here >> http://sqlyogkb.webyog.com/article/159-session-restore

 

 

Regards,

Sibin

[Sibin A S]

Hi Erik,

 

SQLyog reads and presents the DDL information which is returned by executing SHOW CREATE TABLE query of the respective table. It can also be verified by executing the same command (SHOW CREATE TABLE…) from the command line and you may find that the constraint RESTRICT is simply not recorded by the server. 

 

RESTRICT is default action and it does not matter if it is recorded server-side or not. Any other action then RESTRICT should be recorded of course. Therefore for an ON DELETE or ON UPDATE that is not specified, the default action is always RESTRICT.

 

Regards,

Sibin

[Sibin A S]

Hi,

 

Can you please tell us your MySQL server version and also SQLyog version?

 

Regards,

Sibin

[Sibin A S]

Hi,

 

Thanks for your valuable feedback. We have added your request into our issue tracker, here >> https://github.com/webyog/sqlyog-community/issues/2114

 

Regards,

Sibin

[Sibin A S]

Hi Karthikeyan,

 

You may find the SSHD configuration for most of the systems in “/etc/ssh/sshd_config”

 

Are you using public/private keys? If so, you must use keys in the Putty format – not OpenSSH format. We use Plink (a command line utility implementing a subset of Putty) for establishing the tunnel. You can use the ‘puttygen’ utility to convert keys.

 

Regards,

Sibin

[Sibin A S]

Hi Karthikeyan,

 

This error occurs in case of a mismatch in the Username or password. It can also occur if the username is under the ‘DenyUsers’ in the SSHD configuration file. Please refer our FAQ regarding this >> http://faq.webyog.com/22_113_en.html

 

Regards,

Sibin

[Sibin A S]

Hi,

 

You can import only the newly added rows , that is the rows which were not imported in the previous import sessions. You may find the steps which are clearly documented in our SQLyog knowledge base, here >> http://sqlyogkb.webyog.com/article/283-copy-tables-from-the-data-source-incremental-import-sessions

 

Regards,

Sibin

[Sibin A S]

Hello Mitch,

 

If ROW_FORMAT=FIXED is specified while innodb_strict_mode is disabled, InnoDB issues a warning and assumes ROW_FORMAT=COMPACT. If ROW_FORMAT=FIXED is specified while innodb_strict_mode is enabled, which is the default as of MySQL 5.7.7, InnoDB returns an error.

 

You may also refer the MySQL official documentation, here >> https://dev.mysql.com/doc/refman/5.7/en/create-table.html

 

Therefore it is MySQL server that is handling this and not SQLyog. So you may copy the databases with innodb_strict_mode disabled.

 

Regards,

Sibin

[Author]

Posts