Quoting Adrian Klaver <adrian.klaver@aklaver.com>:
> On 3/11/19 9:31 AM, Sonam Sharma wrote:
>> Hi Adrian,
>> Ours is retail company and the DB size is Max 30gb, currently we
>> are using db2.
>
> Things to consider:
>
> 1) Migration tools for DB2 --> MySQL/Postgresql. I have not done
> this, so someone else will have to comment.
>
> 2) The clients/frameworks/ORMs you use now to connect to the
> database. Do they also work with Postgresql/MySQL?
It is also worth to consider if the architecture/model of DB2 fits
PostgreSQL/MySQL. And while at it, how about getting rid of all the
itching quirks of the current solution anyway? I see the danger of
getting disappointed by any of PostgreSQL/MySQL if the current
solution uses DB2 features that cannot be easily mapped to any of the
contenders features.
Bottom line of my insinuation is that the migration tool could be less
an point if you get the opportunity to overhaul your application.
Kind two dimes
Thiemo
--
Signal: +49 1578 7723737
Handys: +41 78 947 36 21 | +49 1578 772 37 37
Tox-Id:
B7282A9E31D944DDAD1ECC5B33C36AAE80B32D119AB7391D602C937A65E8CA0625C495C5322B
