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

Mariano G. · Vor 9 Monate überprüft

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

Alberto C. · Vor 9 Monate überprüft

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

Satish Vithal C. · Vor 9 Monate überprüft

Jess A. · Vor 9 Monate überprüft

Mariano G. · Vor 9 Monate überprüft

Xavier P. · Vor 9 Monate überprüft

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

Alberto C. · Vor 9 Monate überprüft

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

Satish Vithal C. · Vor 9 Monate überprüft

5

Gabriel H. · Vor 9 Monate überprüft

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. · Vor 9 Monate überprüft

5

Gabriel H. · Vor 9 Monate überprüft

Gabriel H. · Vor 9 Monate überprüft

Shubham S. · Vor 9 Monate überprüft

Jean-Michel P. · Vor 9 Monate überprüft

Kausik R. · Vor 9 Monate überprüft

Kausik R. · Vor 9 Monate überprüft

Kausik R. · Vor 9 Monate überprüft

Niskarsha A. · Vor 9 Monate überprüft

Niskarsha A. · Vor 9 Monate überprüft

Niskarsha A. · Vor 9 Monate überprüft

great

Prarthi R. · Vor 9 Monate überprüft

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. · Vor 9 Monate überprüft

Saju S. · Vor 9 Monate überprüft

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. · Vor 9 Monate überprüft

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

Alexey M. · Vor 9 Monate überprüft