Migrate to Cloud SQL for PostgreSQL using Database Migration Service avis

Alvin N. · Examiné il y a 4 mois

Geethanjali B. · Examiné il y a 4 mois

Sumit G. · Examiné il y a 4 mois

bikalpa b. · Examiné il y a 4 mois

Novita A. · Examiné il y a 4 mois

too long though its good

CSE_Subhrajyoti B. · Examiné il y a 4 mois

Nirajn S. · Examiné il y a 4 mois

YASHWANT N. · Examiné il y a 4 mois

フリーズで終了

/ 塙 敏彦 T. · Examiné il y a 4 mois

Sayandeep P. · Examiné il y a 4 mois

Paras G. · Examiné il y a 4 mois

Yash G. · Examiné il y a 4 mois

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. · Examiné il y a 4 mois

Krishnamoorthy T. · Examiné il y a 4 mois

Lalit S. · Examiné il y a 4 mois

Harsh S. · Examiné il y a 4 mois

gourav d. · Examiné il y a 4 mois

Anirudh K. · Examiné il y a 4 mois

Jacob V. · Examiné il y a 4 mois

Gourav D. · Examiné il y a 4 mois

Megha K. · Examiné il y a 4 mois

Ayush S. · Examiné il y a 4 mois

Novita A. · Examiné il y a 4 mois

CHANDRAMOULI D. · Examiné il y a 4 mois

Shravani S. · Examiné il y a 4 mois