[Shadow]

An additional little inconvinience with “copy data to clipboard”: After deselecting the previously mentioned options, the values disappear and enabling them won't make those values reappear!

[Shadow]

And make sure that the appropriate user exists!

[Shadow]

Confirmed with one addition: numeric types are not affected.

[Shadow]

No, the largest actual length is used. Simply create a table with a column of VARCHAR(100) and press F11!

[Shadow]

BTW, what is the version of SQLyog and MySql you use?

[Shadow]

Try creating a user without password and another one with password. If you can login with the password-less user, but cannot with the other one, then you'll need to upgrade SQLyog. Otherwise, it's a different error…

[Shadow]

It's a display problem, was present in previous versions as well. Let's say, you have a table with fields named a, b, c, and a is of text type. If “a” contains any data, then SQLyog appears to expand the size of “a” column to the byte length of the largest entry in “a” field.

[Shadow]

I don't like coffee! 😮

[Shadow]

You should use the SQL WHERE option to make use of the timestamp column. Probably you'll have to write a script that modifies the job file before the sync.

[Shadow]

There is no way to set a proxy in SQLyog. Proxies should be transparent (the communicating apps must not notice its presence) anyway, so configure the proxy correctly.

[Shadow]

max_allowed_packet variable limits the maximum size of SQL statements. Let's say you have a table in which you store pictures in a BLOB column. If you have a max_allowed_packet parameter set to (or left at) 1M then you will not be able to store pictures in this table that exceed 1MB in size, even if the column type allow for more data to be held, as the SQL statement is limited in length. Increasing this parameter has no immediate performance effect because 1. it does not speed up anything, merely allows more data to be sent to MySql in an SQL statement; 2. the buffer is not initialized to this value, buffer of this length is used only when needed.

[Shadow]

Some MySql versions have an exteremely low limit on max_allowed_packet by default!

[Shadow]

Enabling InnoDB does not have anything to do with SQLyog, you have to set certain options in MySql's config file name either my.ini or my.cnf. In windows this file is located either in C: or in Win's own folder.

Following variables must be set (path must be changed, the rest are valid):

innodb_data_file_path = ibdata1:20M:autoextend:max:1000M

innodb_data_home_dir = path

innodb_log_group_home_dir =path

innodb_log_arch_dir =path

set-variable = innodb_mirrored_log_groups=1

set-variable = innodb_log_files_in_group=3

set-variable = innodb_log_file_size=5M

set-variable = innodb_log_buffer_size=2M

innodb_flush_log_at_trx_commit=1

innodb_log_archive=0

set-variable = innodb_buffer_pool_size=10M

set-variable = innodb_additional_mem_pool_size=2M

set-variable = innodb_file_io_threads=4

set-variable = innodb_lock_wait_timeout=50

[Shadow]

Quote:

You said about logging the sql statements, can you tell me how?

Turn on logging in mysql before the sync using log, log_bin or log_update options depending on the MySql's version and turn it off afterwards. Or enable logging all the time, track the start and finish of each sync session and get the needed data out of the log.

[Shadow]

Do you mean getting all those INSERT, UPDATE, DELETE statements sja uses to sync the dbs? Currently you can't do that. You may try logging the SQL statements issued against a MySql server, though.

[Author]

Posts