Migrate MySQL Data to Cloud SQL using Database Migration Service: Challenge Lab Reviews

9250 reviews

Didn't work first time because I didn't use the same names. Everything else was correct

Alberto C. · Reviewed about 1 year ago

not working....Please migrate from the stand alone MySQL database to Cloud SQL.

Satish Vithal C. · Reviewed about 1 year ago

Jess A. · Reviewed about 1 year ago

Mariano G. · Reviewed about 1 year ago

Xavier P. · Reviewed about 1 year ago

Can't make it work. Database is created, data migrated, confirmed with sql. Task 2 won't pass

Alberto C. · Reviewed about 1 year ago

not working....Please migrate from the stand alone MySQL database to Cloud SQL.

Satish Vithal C. · Reviewed about 1 year ago

Gabriel H. · Reviewed about 1 year ago

I don't know why I don't have enough time, the creation of profiles and jobs is very slow. They do not refresh the steps

Alejandro R. · Reviewed about 1 year ago

Gabriel H. · Reviewed about 1 year ago

Shubham S. · Reviewed about 1 year ago

Jean-Michel P. · Reviewed about 1 year ago

Kausik R. · Reviewed about 1 year ago

Niskarsha A. · Reviewed about 1 year ago

great

Prarthi R. · Reviewed about 1 year ago

update: I managed to get through but the check is really buggy. It expects the *migration jobs* to be named mysql-pln-zxf (and cont) which is not part of the task! (those are the names of Cloud SQL DBs) -- i.e. naming DBs correctly but jobs differently will never yield success ib this Lab. Very confusing and incorrect assessment of results. This was a frustrating lab. I performed both migrations successfully twice but the checker was not able to verify the work. I have verified on both migrations that the mysql db was migrated correctly and that cont migration is working (by update and check). Also All relevant logs have been generated, so why does the validation check not work, twice? frustrating.

Amine C. · Reviewed about 1 year ago

Saju S. · Reviewed about 1 year ago

This was a frustrating lab. I performed both migrations successfully twice but the checker was not able to verify the work. I have verified on both migrations that the mysql db was migrated correctly and that cont migration is working (by update and check). Also All relevant logs have been generated, so why does the validation check not work, twice? frustrating.

Amine C. · Reviewed about 1 year ago

it's very strange that migration job must have the same name as a destination database,othewise checkpoint 2 is not accepted

Alexey M. · Reviewed about 1 year ago

Anatoliy A. · Reviewed about 1 year ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.