From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: New Oracle system in our house, migration chances |
Date: | 2022-01-13 15:06:47 |
Message-ID: | d2d5f56c-f2e3-3eea-5364-f3bfb8138e67@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 1/13/22 8:15 AM, Achilleas Mantzios wrote:
> On 13/1/22 4:12 μ.μ., Kenneth Marshall wrote:
>>>> Hi Achilleas,
>>>> I would go with version B - since as I understand it's ISV
>>>> solution. Meaning the postgres ddl was tested and aligned with the
>>>> application layer, otherwise you would need to fix app layer after
>>>> the migration.
>>> Dziekuje Alicija. The powerbuilder app is in-house developed, source
>>> is available, what could be wrong with the app? Browsing through the
>>> powerbuilder source I don't see (by eye) anything that could break
>>> something in PgSQL.
>>> --
>>> Achilleas Mantzios
>>> DBA, Analyst, IT Lead
>>> IT DEPT
>>> Dynacom Tankers Mgmt
>> Hi Achilleas,
>>
>> If the schema and usage is straight-forward, I would recommend using
>> ora2pg to give you an estimation cost for your migration by letting you
>> know what cannot be automatically translated. Once you have that you
>> will be better informed as to the work needed.
> Thank you Ken!
ora2pg worked perfectly for us in migrating 8TB of Oracle 11 data and simple
triggers to Pg 12.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Alicja Kucharczyk | 2022-01-13 15:18:08 | Re: New Oracle system in our house, migration chances |
Previous Message | Alicja Kucharczyk | 2022-01-13 15:02:36 | Re: New Oracle system in our house, migration chances |