| From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Alicja Kucharczyk <zaledwie10minut(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: New Oracle system in our house, migration chances |
| Date: | 2022-01-13 14:20:02 |
| Message-ID: | 31fdaf33-f401-20ab-9f98-5bedb88448d9@matrix.gatewaynet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 13/1/22 4:13 μ.μ., Julien Rouhaud wrote:
> On Thu, Jan 13, 2022 at 04:06:06PM +0200, Achilleas Mantzios wrote:
>> 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.
> I would go with option A if possible. If you want to get an idea of how
> complicated a migration would be, ora2pg does have a migration cost assessment
> report [1]. It can even check the queries if you have the audit trail enabled
> on your oracle database (if that existed in that version).
>
> [1] https://ora2pg.darold.net/documentation.html#Migration-cost-assessment
Such great info. Thank you so much. 21 years ago we started building our system on top of PostgreSQL, there have been challenges, but we never regreted our initial decision (vs mysql) not even once.
--
Achilleas Mantzios
DBA, Analyst, IT Lead
IT DEPT
Dynacom Tankers Mgmt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MichaelDBA | 2022-01-13 14:28:41 | Re: New Oracle system in our house, migration chances |
| Previous Message | Achilleas Mantzios | 2022-01-13 14:15:57 | Re: New Oracle system in our house, migration chances |