Migrate to Cloud SQL for PostgreSQL using Database Migration Service Reviews

Simranjeet S. · Reviewed 4 أشهر ago

長い。接続された、とでて進めたら接続されてないようで終了

/ 塙 敏彦 T. · Reviewed 4 أشهر ago

Ajie N. · Reviewed 4 أشهر ago

チェックがでない

/ 塙 敏彦 T. · Reviewed 4 أشهر ago

チェックがでない

/ 塙 敏彦 T. · Reviewed 4 أشهر ago

Sivakumar V. · Reviewed 4 أشهر ago

Teymur O. · Reviewed 4 أشهر ago

20240731

Kamel S. · Reviewed 4 أشهر ago

Eve E. · Reviewed 4 أشهر ago

joice l. · Reviewed 4 أشهر ago

ok

Malakari S. · Reviewed 4 أشهر ago

Pablo Andres G. · Reviewed 4 أشهر ago

succesfull after multiple attempts.

Garrett S. · Reviewed 4 أشهر ago

Lalit S. · Reviewed 4 أشهر ago

ok

Malakari S. · Reviewed 4 أشهر ago

Radhish A. · Reviewed 4 أشهر ago

NA

Mohit G. · Reviewed 4 أشهر ago

Bruno L. · Reviewed 4 أشهر ago

Anik P. · Reviewed 4 أشهر ago

good lab

Paresh P. · Reviewed 4 أشهر ago

Smriti V. · Reviewed 4 أشهر ago

Lipsa Priyadarshini M. · Reviewed 4 أشهر 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 4 أشهر ago

Pierre S. · Reviewed 4 أشهر ago

Bhuvan P. · Reviewed 4 أشهر ago