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