public inbox for [email protected]
help / color / mirror / Atom feedHow to handle application connectivity change when moving from Oracle to Postgres in GCP
3+ messages / 3 participants
[nested] [flat]
* How to handle application connectivity change when moving from Oracle to Postgres in GCP
@ 2023-09-10 17:43 kunwar singh <[email protected]>
2023-09-10 17:55 ` Re: How to handle application connectivity change when moving from Oracle to Postgres in GCP Erik Brandsberg <[email protected]>
2023-09-10 18:32 ` RE: How to handle application connectivity change when moving from Oracle to Postgres in GCP Mike Sofen <[email protected]>
0 siblings, 2 replies; 3+ messages in thread
From: kunwar singh @ 2023-09-10 17:43 UTC (permalink / raw)
To: [email protected]
Hi Listers,
Say we have this App->DB connectivity Model.
APP1
Contains synonyms which point to objects under APP1.
APPOWN
Contains the tables, indexes
And it is a Java application that connects to APP1.
Now when the database is switched from Oracle 19c onprem to CloudSQL
Postgres say v15.
Questions that I have:
1. What needs to be done at the database end in terms of schema setup in
order to ensure the application is able to connect to the relevant tables
without any concerns?
2. Do I need to create users APP1 and APPOWN in postgres? If so, what
privileges are required to be assigned to these?
3. How to tie them with service accounts?
4. With which username/service account does the application make
connection to the database?
I still don't understand user/schema concepts in postgres tbh as I'm
still a noob :)
--
Cheers,
Kunwar
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: How to handle application connectivity change when moving from Oracle to Postgres in GCP
2023-09-10 17:43 How to handle application connectivity change when moving from Oracle to Postgres in GCP kunwar singh <[email protected]>
@ 2023-09-10 17:55 ` Erik Brandsberg <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Erik Brandsberg @ 2023-09-10 17:55 UTC (permalink / raw)
To: kunwar singh <[email protected]>; +Cc: [email protected]
Keep in mind that it is likely that a significant portion of the data
access code may need to be rewritten unless you are using an ORM that does
the conversion for you. Most apps can't be migrated directly from Oracle
to Postgres. Based on the questions you are asking, I seriously suggest
you contact a company that assists with migrations in order to answer your
questions and highlight the issues you may be facing.
On Sun, Sep 10, 2023 at 1:43 PM kunwar singh <[email protected]>
wrote:
> Hi Listers,
>
> Say we have this App->DB connectivity Model.
>
> APP1
> Contains synonyms which point to objects under APP1.
>
> APPOWN
> Contains the tables, indexes
>
> And it is a Java application that connects to APP1.
>
> Now when the database is switched from Oracle 19c onprem to CloudSQL
> Postgres say v15.
> Questions that I have:
>
> 1. What needs to be done at the database end in terms of schema setup in
> order to ensure the application is able to connect to the relevant tables
> without any concerns?
> 2. Do I need to create users APP1 and APPOWN in postgres? If so, what
> privileges are required to be assigned to these?
> 3. How to tie them with service accounts?
> 4. With which username/service account does the application make
> connection to the database?
>
> I still don't understand user/schema concepts in postgres tbh as I'm
> still a noob :)
>
>
>
> --
> Cheers,
> Kunwar
>
^ permalink raw reply [nested|flat] 3+ messages in thread
* RE: How to handle application connectivity change when moving from Oracle to Postgres in GCP
2023-09-10 17:43 How to handle application connectivity change when moving from Oracle to Postgres in GCP kunwar singh <[email protected]>
@ 2023-09-10 18:32 ` Mike Sofen <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Mike Sofen @ 2023-09-10 18:32 UTC (permalink / raw)
To: 'kunwar singh' <[email protected]>; [email protected]
From: kunwar singh <[email protected]> Sent: Sunday, September 10, 2023 10:43 AM
To: [email protected]
Subject: How to handle application connectivity change when moving from Oracle to Postgres in GCP
Hi Listers,
Say we have this App->DB connectivity Model.
APP1
Contains synonyms which point to objects under APP1.
APPOWN
Contains the tables, indexes
And it is a Java application that connects to APP1.
Now when the database is switched from Oracle 19c onprem to CloudSQL Postgres say v15.
Questions that I have:
1. What needs to be done at the database end in terms of schema setup in order to ensure the application is able to connect to the relevant tables without any concerns?
2. Do I need to create users APP1 and APPOWN in postgres? If so, what privileges are required to be assigned to these?
3. How to tie them with service accounts?
4. With which username/service account does the application make connection to the database?
I still don't understand user/schema concepts in postgres tbh as I'm still a noob :)
--
Cheers,
Kunwar
Kunwar,
Since you mentioned CloudSQL (Google Cloud’s db platform for postgres, mysql, and sql server), I recommend contacting your rep at Google Cloud on this topic. They just went GA on their DMS product (Data Migration Service) for Oracle to CloudSQL-Postgres migrations (and AlloyDB shortly) – pretty good timing. DMS converts schema and code, understands most permissions and security pieces, and most importantly, has great tech support. Usually there is no charge for using DMS (Google underwrites the cost since you’re migrating to their platform).
Mike
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2023-09-10 18:32 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-09-10 17:43 How to handle application connectivity change when moving from Oracle to Postgres in GCP kunwar singh <[email protected]>
2023-09-10 17:55 ` Erik Brandsberg <[email protected]>
2023-09-10 18:32 ` Mike Sofen <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox