Migration Job Starts But…

[Richard J Lacroix]

I had been happily importing tables from a MS SQL database all day yesterday but suddenly with the import of one table, the PowerTool reports that the Job has started but I see no row import reported.

Thinking it was just a slow network connection, I kicked off the job again and left for the day.

I returned this morning and still nothing had been imported, the log says the Job had started and the Next button was no longer greyed out but no data had actually been imported.

I restarted SQLyog and tried the import again, then tried a couple of different tables but all with the same result. The job starts, the Next button is no longer grey, the Terminate button never shows up and no data is imported.

Help! I still have 30 tables to go and a deadline! Has anyone observed this behavior and more importantly, does anyone know of a remedy?

:wacko:

[peterlaursen]

First: did you update any softwaree in between when it worked and when it did not?

What is the SQLyog version?

But basically we will need a 'reproducable test case'.

We could start with the job file. If you do not want to expose your data in public then create a ticket

[Richard J Lacroix]

No software updates

SQL yog 5.19 Enterprise

The job is actually being kicked off using a SQL statement, since using the wizard errors out because the tables all have auto_increment fields. The statement is simply “select * from bh_Client”, after successfully importing 5 more tables this morning, I am now looking into the table structures of the ones that the Job isn't importing to see if there is something unsual or different about them.

[Author]

Posts