Don't kid yourself. MS Sql Server is different enough to Oracle that someone
not versed in SQL Server will have extensive training.
Just one
example:
With MS SQL Server there is a locking situation if someone simply
even reads a table. So a standard practice is (has been?) to create a temporary
table for your work, take a copy of what you need from the primary table to the
temp table, do your work in the temp table, when you are finished copy the data
back to the main.
That way you only lock the main table briefly to read the
dataset and update the data set. You don't lock it for the total time of your
processing.
Any Oracle Dev unaware of such differences (and this
developer was only aware because another developer was and pointed it out as one
of the many huge differences) will have a big learning curve ahead of
them.
My main point being: it doesn't matter what you switch too, odds
are extensive retraining costs are involved. So it's not really a "negative
switching to X that does not apply to switching to MS Sql Server" as your "on
one hand" seems to allude to.
RAS[ Reply to This | Parent | # ]
| 
