Migrate to Cloud SQL for PostgreSQL using Database Migration Service Reviews

NA

Mohit G. · Reviewed yaklaşık 1 yıl ago

Bruno L. · Reviewed yaklaşık 1 yıl ago

Anik P. · Reviewed yaklaşık 1 yıl ago

good lab

Paresh P. · Reviewed yaklaşık 1 yıl ago

Smriti V. · Reviewed yaklaşık 1 yıl ago

Lipsa Priyadarshini M. · Reviewed yaklaşık 1 yıl 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 yaklaşık 1 yıl ago

Pierre S. · Reviewed yaklaşık 1 yıl ago

Bhuvan P. · Reviewed yaklaşık 1 yıl ago

Alvin N. · Reviewed yaklaşık 1 yıl ago

Geethanjali B. · Reviewed yaklaşık 1 yıl ago

Sumit G. · Reviewed yaklaşık 1 yıl ago

bikalpa b. · Reviewed yaklaşık 1 yıl ago

Novita A. · Reviewed yaklaşık 1 yıl ago

too long though its good

CSE_Subhrajyoti B. · Reviewed yaklaşık 1 yıl ago

Nirajn S. · Reviewed yaklaşık 1 yıl ago

YASHWANT N. · Reviewed yaklaşık 1 yıl ago

フリーズで終了

/ 塙 敏彦 T. · Reviewed yaklaşık 1 yıl ago

Sayandeep P. · Reviewed yaklaşık 1 yıl ago

Paras G. · Reviewed yaklaşık 1 yıl ago

Yash G. · Reviewed yaklaşık 1 yıl 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 yaklaşık 1 yıl ago

Krishnamoorthy T. · Reviewed yaklaşık 1 yıl ago

Lalit S. · Reviewed yaklaşık 1 yıl ago

Harsh S. · Reviewed yaklaşık 1 yıl ago