Migrar para o Cloud SQL para PostgreSQL usando o Database Migration Service avaliações

Simranjeet S. · Revisado há 4 months

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

/ 塙 敏彦 T. · Revisado há 4 months

Ajie N. · Revisado há 4 months

チェックがでない

/ 塙 敏彦 T. · Revisado há 4 months

チェックがでない

/ 塙 敏彦 T. · Revisado há 4 months

Sivakumar V. · Revisado há 4 months

Teymur O. · Revisado há 4 months

20240731

Kamel S. · Revisado há 4 months

Eve E. · Revisado há 4 months

joice l. · Revisado há 4 months

ok

Malakari S. · Revisado há 4 months

Pablo Andres G. · Revisado há 4 months

succesfull after multiple attempts.

Garrett S. · Revisado há 4 months

Lalit S. · Revisado há 4 months

ok

Malakari S. · Revisado há 4 months

Radhish A. · Revisado há 4 months

NA

Mohit G. · Revisado há 4 months

Bruno L. · Revisado há 4 months

Anik P. · Revisado há 4 months

good lab

Paresh P. · Revisado há 4 months

Smriti V. · Revisado há 4 months

Lipsa Priyadarshini M. · Revisado há 4 months

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. · Revisado há 4 months

Pierre S. · Revisado há 4 months

Bhuvan P. · Revisado há 4 months