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

lab issues when migration job / connection profiles names are different than source/target instances

Oskar K. · Reviewed 2 yıldan fazla ago

quite hard

Dodzi A. · Reviewed 2 yıldan fazla ago

Mariana A. · Reviewed 2 yıldan fazla ago

Anrie S. · Reviewed 2 yıldan fazla ago

Vinicius S. · Reviewed 2 yıldan fazla ago

Felipe S. · Reviewed 2 yıldan fazla ago

Lab is broken!

Ossie B. · Reviewed 2 yıldan fazla ago

Soumen C. · Reviewed 2 yıldan fazla ago

Avisek K. · Reviewed 2 yıldan fazla ago

Monika G. · Reviewed 2 yıldan fazla ago

Rohan P. · Reviewed 2 yıldan fazla ago

Soumen C. · Reviewed 2 yıldan fazla ago

Avisek K. · Reviewed 2 yıldan fazla ago

Artur K. · Reviewed 2 yıldan fazla ago

Gustavo Alberto V. · Reviewed 2 yıldan fazla ago

Artur K. · Reviewed 2 yıldan fazla ago

Vakcharla R. · Reviewed 2 yıldan fazla ago

Beth D. · Reviewed 2 yıldan fazla ago

Juan Alejandro O. · Reviewed 2 yıldan fazla ago

OK

Jarosław K. · Reviewed 2 yıldan fazla ago

I migrade 2x my stand alone to Cloud SQl sadly unable to positive check it. Name of migration job need to be that same as creating instance with is not written in task.

Mateusz K. · Reviewed 2 yıldan fazla ago

Task 1 EXPLICITLY mentioned using the EXTERNAL IP Address of the VM Instance. I followed this instruction for two attempts that failed. Every other lab with a similar setup used the INTERNAL IP address instead. I used it in this last attempt and the lab finally completed.

Jose Alfron B. · Reviewed 2 yıldan fazla ago

Santhosh Kumar M. · Reviewed 2 yıldan fazla ago

Yuriy L. · Reviewed 2 yıldan fazla ago

Jean-Luc A. · Reviewed 2 yıldan fazla ago