| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(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:13:21 |
| Message-ID: | 20220113141321.qdas6evcuc5vvfvp@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2022-01-13 14:15:57 | Re: New Oracle system in our house, migration chances |
| Previous Message | Kenneth Marshall | 2022-01-13 14:12:41 | Re: New Oracle system in our house, migration chances |