| From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(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 14:54:05 |
| Message-ID: | 28f5dfe5-fdf6-5d25-8fbf-77075a55a28c@matrix.gatewaynet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 13/1/22 4:51 μ.μ., Thomas Kellerer wrote:
> Julien Rouhaud schrieb am 13.01.2022 um 15:13:
>> 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).
>>
> I second this. Option A) is much cleaner. In my experience compatibility layers
> that promise that "System A" behaves exactly like "System B" also introduce
> a lot of additional problems. And if something goes wrong, you can never be sure
> which part causes the problem.
Thanks, of course I agree with the last sentence.
>
>
>
--
Achilleas Mantzios
DBA, Analyst, IT Lead
IT DEPT
Dynacom Tankers Mgmt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alicja Kucharczyk | 2022-01-13 15:02:36 | Re: New Oracle system in our house, migration chances |
| Previous Message | Thomas Kellerer | 2022-01-13 14:51:43 | Re: New Oracle system in our house, migration chances |