[Suzette]

peterlaursen wrote on May 18 2006, 05:33 PM:

” but how do I know if BETA or FINAL?”

program help .. about tells. But if you DL'ed from that link today it is the FINAL.

The problem is the connection to MySQL. And it is on 'localhost'.

hmmm … it can be hardware related (motherboard, harddisk) or software (protocol stack) related. It also can be an issue with MySQL 5.1 or SQLyog. Very hard to tell. Thinking ….

Running jobs like Migration, Sync etc will always demand a more stable connection that GUI operations do. Do you have a chance to test on another PC?

All these tests were on my laptop with 1G RAM. I also tested on desktop with 2G RAM. Same thing happens. I'm thinking it has to do with partitioning in conjunction with large number of columns? As I said earlier, without migrating to a partitioned table, imports fine. It is only when I add the partition to the table that I get this error. hmmm…perhaps i should send email to mysql 5.1 folks? Is there a way to run this from the command line?

[Suzette]

peterlaursen wrote on May 18 2006, 05:15 PM:

No, it is not related to partitioning, I think. 'Sorting data into partitions' is done by the MySQL server itself. The SQL that SQLyog must generate is the same with and without partitions on the target.

“ERROR: 2006, MySQL server has gone away”

Are you using 5.12 FINAL and not a beta??

5.12 will reconnect if connection is lost. But of course there are limits to how unstable connection can be for it to work.

How do you connect to MySQL. Direct, HTTP, SSH ?

This is probably a dumb question, but how do I know if BETA or FINAL? I received an upgrade email today from Webyog giving me a link for the enterprise download (http://www.webyog.com/sqlyog/183E427A-808F-4CB9-BE5B-06T0D2C8CC48/SQLyog512Ent.exe).

I'm connecting directly to my localhost MySQL database from SQLYOG. I don't believe any HTTP or SSH. From SQLYOG I use Migration Tookit using ODBC to connect to RedBrick database to get the data.

This is the same connection method for all my tests I indicated in previous reply.

[Suzette]

Ritesh wrote on May 4 2006, 02:34 AM:

http://www.webyog.com/forums/index.php?sho…view=getnewpost

I am getting the same 2006 error. Some background. Using Migration Toolkit to connect with ODBC to IBM Redbrick database on Windows server. I have a very large table (500 columns, 1M rows).

Test #1. I let toolkit create the table and load the data. I am using a WHERE clause to limit to 100K records. Works just dandy.

Test #2. I drop this table. I recreate the table using MySQL 5.1 so I can use partitions. I create the table with 10 partitions using KEY() as the partition. I use Migration Toolkit. Go into Advanced to click on import data only (don't want toolkit dropping table and recreating because I need these partitions). I use the same WHERE clause as in Test #1 above. This is what I get:

*********************************************************

SQLyog Job Agent Version 5.12

Copyright © Webyog Softworks Pvt. Ltd.. All Rights Reserved.

Job started at Thu May 18 12:20:04 2006

DBMS Information: RED BRICK WAREHOUSE

Importing table schema: UNIT_FACT… Successful…

Importing table foreign keys: UNIT_FACT… Successful…

Importing table data: UNIT_FACT…

ERROR: 2006, MySQL server has gone away

Table:UNIT_FACT

Check C:Program FilesSQLyog Enterprisesja.log for complete error details.

ERROR: 2006, MySQL server has gone away

Table:UNIT_FACT

Check C:Program FilesSQLyog Enterprisesja.log for complete error details.

ERROR: Import aborted…

Check C:Program FilesSQLyog Enterprisesja.log for complete error details.

Total time taken – 11 sec(s)

*********************************************************

Test #3: I create a smaller table which only has 25 fields and 1M records. I create 10 partitions using KEY(). I use Migration Toolkit, click on import data only. No WHERE clause. The data comes over fine and the 10 partition files are what I would expect.

Question: What's happening? It seems like the partitioning of tables with a large number of columns is what is making it exit abnormally. Any hints? This is a major stumbling block in our endeavor to migrate to MySQL so your help would be much appreciated.

Thanks….SBW

[Author]

Posts