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

8555 opiniones

Mariano G. · Se revisó hace 9 meses

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

Alberto C. · Se revisó hace 9 meses

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

Satish Vithal C. · Se revisó hace 9 meses

Jess A. · Se revisó hace 9 meses

Mariano G. · Se revisó hace 9 meses

Xavier P. · Se revisó hace 9 meses

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

Alberto C. · Se revisó hace 9 meses

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

Satish Vithal C. · Se revisó hace 9 meses

Gabriel H. · Se revisó hace 9 meses

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. · Se revisó hace 9 meses

Gabriel H. · Se revisó hace 9 meses

Shubham S. · Se revisó hace 9 meses

Jean-Michel P. · Se revisó hace 9 meses

Kausik R. · Se revisó hace 9 meses

Niskarsha A. · Se revisó hace 9 meses

great

Prarthi R. · Se revisó hace 9 meses

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. · Se revisó hace 9 meses

Saju S. · Se revisó hace 9 meses

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. · Se revisó hace 9 meses

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

Alexey M. · Se revisó hace 9 meses

No garantizamos que las opiniones publicadas provengan de consumidores que hayan comprado o utilizado los productos. Google no verifica las opiniones.