Migrate to Cloud SQL for PostgreSQL Using Database Migration Service Reviews

Smriti V. · Reviewed over 1 year ago

Lipsa Priyadarshini M. · Reviewed over 1 year ago

Good exercise but several errors in content. - There is no "Routes" tab in the service networking side, you have to find it through "Managed Routes". - Restricting pg configuration to the peered range in the tutorial never restarted PG service (only started due to error in shown command, and it was already running so no effect). - When you actually use the proper restart command like earlier in the tutorial when changing the config for the first time, that then breaks the later step in the tutorial to connect through Cloud Shell psql client, as now the peering range whitelist is in effect. - Data confirmation step did never confirm the assessment even though data was there, possibly because I had to re-do the migration job to a new instance as I typo'd the name. - The names could be more uniform in this sense as well (postgres vs postgresql prefixing). The pglogical setup does not conform to current Google recommendation either (in SQL statements used).

Mikael Z. · Reviewed over 1 year ago

Pierre S. · Reviewed over 1 year ago

Bhuvan P. · Reviewed over 1 year ago

Alvin N. · Reviewed over 1 year ago

Geethanjali B. · Reviewed over 1 year ago

Sumit G. · Reviewed over 1 year ago

bikalpa b. · Reviewed over 1 year ago

Novita A. · Reviewed over 1 year ago

too long though its good

CSE_Subhrajyoti B. · Reviewed over 1 year ago

Nirajn S. · Reviewed over 1 year ago

YASHWANT N. · Reviewed over 1 year ago

フリーズで終了

/ 塙 敏彦 T. · Reviewed over 1 year ago

Sayandeep P. · Reviewed over 1 year ago

Paras G. · Reviewed over 1 year ago

Yash G. · Reviewed over 1 year ago

Good exercise but several errors in content. - There is no "Routes" tab in the service networking side, you have to find it through "Managed Routes". - Restricting pg configuration to the peered range in the tutorial never restarted PG service (only started due to error in shown command, and it was already running so no effect). - When you actually use the proper restart command like earlier in the tutorial when changing the config for the first time, that then breaks the later step in the tutorial to connect through Cloud Shell psql client, as now the peering range whitelist is in effect. - Data confirmation step did never confirm the assessment even though data was there, possibly because I had to re-do the migration job to a new instance as I typo'd the name. - The names could be more uniform in this sense as well (postgres vs postgresql prefixing). The pglogical setup does not conform to current Google recommendation either (in SQL statements used).

Mikael Z. · Reviewed over 1 year ago

Krishnamoorthy T. · Reviewed over 1 year ago

Lalit S. · Reviewed over 1 year ago

Harsh S. · Reviewed over 1 year ago

gourav d. · Reviewed over 1 year ago

Anirudh K. · Reviewed over 1 year ago

Jacob V. · Reviewed over 1 year ago

Gourav D. · Reviewed over 1 year ago