Some things cannot be avoided. I am getting involved in a conversion from DB2 to ms-sql
In the current situation I've got ksh-scripts which produce SQL and this SQL is fed into db2batch. All this on aix.
I am planning to convert my ksh-scripts into perl and use standard ODBC to communicate with DB2. The scripts will run on windows. Code SQL as agile as possible so in the next phase the ODBC can point to ..... the other database... <sigh> and the conversion is a fact.
But my hemlock is not empty yet. They would rather see a powershell solution. So I need arguments why perl is much betten than powershell. I do not know powershell and I was not planning to educate myself...
Is that wise or are powershell skills usefull for a DB2/DBA?
Please advise.
O and while we're at it: which is better on windows: activeState or strawberry perl?