Migrate to Cloud SQL for PostgreSQL using Database Migration Service Reviews
24457 reviews
Radhish A. · Reviewed about 1 year ago
NA
Mohit G. · Reviewed about 1 year ago
Bruno L. · Reviewed about 1 year ago
Anik P. · Reviewed about 1 year ago
good lab
Paresh P. · Reviewed about 1 year ago
Smriti V. · Reviewed about 1 year ago
Lipsa Priyadarshini M. · Reviewed about 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 about 1 year ago
Pierre S. · Reviewed about 1 year ago
Bhuvan P. · Reviewed about 1 year ago
Alvin N. · Reviewed about 1 year ago
Geethanjali B. · Reviewed about 1 year ago
Sumit G. · Reviewed about 1 year ago
bikalpa b. · Reviewed about 1 year ago
Novita A. · Reviewed about 1 year ago
too long though its good
CSE_Subhrajyoti B. · Reviewed about 1 year ago
Nirajn S. · Reviewed about 1 year ago
YASHWANT N. · Reviewed about 1 year ago
フリーズで終了
/ 塙 敏彦 T. · Reviewed about 1 year ago
Sayandeep P. · Reviewed about 1 year ago
Paras G. · Reviewed about 1 year ago
Yash G. · Reviewed about 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 about 1 year ago
Krishnamoorthy T. · Reviewed about 1 year ago
Lalit S. · Reviewed about 1 year ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.