How can we help you today? How can we help you today?
bstewart
Sorry, I should have mentioned the version number. 1.0.0.409 which should be the latest version (running on Win 7 Enterprise SP1 x64). / comments
Sorry, I should have mentioned the version number. 1.0.0.409 which should be the latest version (running on Win 7 Enterprise SP1 x64).
0 votes
Another quick update here. I've noticed that queries involving the information_schema database on the server in question are very slow which would suggest the problem doesn't lie with MySQL compare. / comments
Another quick update here. I've noticed that queries involving the information_schema database on the server in question are very slow which would suggest the problem doesn't lie with MySQL compare.
0 votes
Unfortunately, the log doesn't reveal much other than how long each part of the comparison is taking: 13:03:01.683|Debug |PopulationLogger |5 |ProgressTask:Populating DB test1 13:03:01.687|Debug |PopulationLogger |5 |ProgressTask:Populating Dependencies 13:03:08.793|Debug |PopulationLogger |5 |ProgressTask:Populating Tables 13:03:11.373|Debug |PopulationLogger |5 |ProgressTask:Populating Columns 13:03:11.549|Debug |PopulationLogger |5 |ProgressTask:Populating Indexes 13:03:14.031|Debug |PopulationLogger |5 |ProgressTask:Populating Constraints 13:03:14.031|Debug |PopulationLogger |5 |ProgressTask:Populating Index Constraints 13:03:41.769|Debug |PopulationLogger |5 |ProgressTask:Populating FK Constraints 13:04:31.104|Debug |PopulationLogger |5 |ProgressTask:Populating Views 13:04:31.155|Debug |PopulationLogger |5 |ProgressTask:Populating Routines 13:04:31.180|Debug |PopulationLogger |5 |ProgressTask:Populating Triggers 13:04:32.511|Debug |PopulationLogger |5 |ProgressTask:Populating Events 13:04:32.536|Debug |PopulationLogger |5 |ProgressTask:Populating DB test2 13:04:32.536|Debug |PopulationLogger |5 |ProgressTask:Populating Dependencies 13:04:37.949|Debug |PopulationLogger |5 |ProgressTask:Populating Tables 13:04:40.106|Debug |PopulationLogger |5 |ProgressTask:Populating Columns 13:04:40.263|Debug |PopulationLogger |5 |ProgressTask:Populating Indexes 13:04:43.214|Debug |PopulationLogger |5 |ProgressTask:Populating Constraints 13:04:43.214|Debug |PopulationLogger |5 |ProgressTask:Populating Index Constraints 13:05:08.606|Debug |PopulationLogger |5 |ProgressTask:Populating FK Constraints 13:05:58.547|Debug |PopulationLogger |5 |ProgressTask:Populating Views 13:05:58.582|Debug |PopulationLogger |5 |ProgressTask:Populating Routines 13:05:58.586|Debug |PopulationLogger |5 |ProgressTask:Populating Triggers 13:05:59.877|Debug |PopulationLogger |5 |ProgressTask:Populating Events 13:06:00.948|Debug |Event Aggregator |1 |:Sending message #Limb.#paD 13:06:01.285|Debug |Event Aggregator |1 |:Sending message #Limb.#pbD 13:06:02.674|Debug |Event Aggregator |1 |:Sending message #Limb.#obD / comments
Unfortunately, the log doesn't reveal much other than how long each part of the comparison is taking: 13:03:01.683|Debug |PopulationLogger |5 |ProgressTask:Populating DB test1 13:03:01.687|Deb...
0 votes
I should also note that my network connection to the server is generally good. Pings are always < 1ms and I can transfer a 900MB ISO file in < 20 seconds. / comments
I should also note that my network connection to the server is generally good. Pings are always < 1ms and I can transfer a 900MB ISO file in < 20 seconds.
0 votes
Michael Christofides wrote: Sorry for the delay, but the recent release should contain a fix for this issue. Please do let us know! I downloaded the new version and this does seem to be fixed now. Thanks. / comments
Michael Christofides wrote: Sorry for the delay, but the recent release should contain a fix for this issue. Please do let us know! I downloaded the new version and this does seem to be fixed...
0 votes
I'm still seeing this problem. I recently bough MySQL Compare using version 1.0.0.301 and appear to be up to date (running Help->Check For Updates says no updates available). As a quick test, I created two databases - `db1` and `db2`. Now run this: CREATE TABLE `db1`.`test` &#40; `id` INT&#40;10&#41; NOT NULL AUTO_INCREMENT, `name` VARCHAR&#40;10&#41; NULL, `active` TINYINT NOT NULL DEFAULT '1', PRIMARY KEY &#40;`id`&#41; &#41; COLLATE='latin1_swedish_ci' ENGINE=InnoDB; CREATE TABLE `db2`.`test` &#40; `id` INT&#40;10&#41; NOT NULL AUTO_INCREMENT, `name` VARCHAR&#40;10&#41; NULL, PRIMARY KEY &#40;`id`&#41; &#41; COLLATE='latin1_swedish_ci' ENGINE=InnoDB; Upon running a comparison of the two databases, it correctly identifies the new `active` column and shows it as: `active` tinyint(4) NOT NULL DEFAULT 1, Upon running the deployment I get a "No value specified for a NOT NULL column". Here I have to manually change the dropdown to "Specify custom value" and change the value to 1. In a simple example like this, that's not too much of a hassle but when you're using this for larger deployments, this can become quite annoying if there are lots of new NOT NULL columns with DEFAULT values specified. / comments
I'm still seeing this problem. I recently bough MySQL Compare using version 1.0.0.301 and appear to be up to date (running Help->Check For Updates says no updates available). As a quick test, I cre...
0 votes