You want to migrate your PostgreSQL database from another cloud provider to Cloud SQL. You plan on using Database Migration Service and need to assess the impact of any known limitations. What should you do? (Choose two.)
I feel pretty confident about this one. Identifying the table count, missing primary keys, and missing foreign keys are all important steps to assess the migration impact. I'll make sure to cover those bases.
This seems straightforward enough. I'll focus on the key things to check - table count, primary keys, and foreign keys. That should give me a good idea of any potential issues before the migration.
I'm a bit confused on the encryption part. Do I need to identify if the source database is using pgcrypto or customer-managed encryption keys? I'll have to research that more.
Okay, let's think this through step-by-step. First, I'll need to check if the database has over 512 tables, as that's a known limitation. Then I'll look for any tables without primary keys or foreign keys.
Hmm, this looks like a tricky one. I'll need to carefully review the limitations of the Database Migration Service to see what potential issues I might encounter.
Wait, did they say 'Database Migration Service'? I thought we were moving to Cloud SQL, not the cloud migration service. Guess I need to brush up on my cloud skills!
Art
3 months agoVal
3 months agoOwen
3 months agoFabiola
4 months agoGlenna
4 months agoBuffy
4 months agoDianne
4 months agoClarinda
4 months agoJacki
5 months agoTricia
5 months agoDenny
5 months agoErnestine
5 months agoCandra
5 months agoValentin
5 months agoEvan
10 months agoDorothy
9 months agoMiriam
9 months agoMacy
10 months agoLynna
9 months agoDannie
9 months agoJarvis
9 months agoLeota
10 months agoKing
10 months agoRusty
10 months agoLisha
10 months agoAlpha
10 months agoJanessa
9 months agoJanessa
9 months agoChana
10 months ago