Appreciate your comments on Database migration from Oracle to SQL Server ...
From my perspective, there are two major known issues that would cause major
resource consumption for porting My-App from Oracle to Microsoft SQL Server. First,
the Perl code within My-App reads the Oracle object meta-data for defining it's
internal objects and data types. SD would be the best group to identify the effort
to replace this dynamic functionality. The second issue is the coding required
to replace Oracle's built-in functionality to work with data hierarchies / tree
structures / parent-child relationships.
The My-App Data Model is heavily based on parent-child relationships through out
numerous tables; every item has a parent, every person has a manager, every team
may or may not be nested, etc. Oracle has native SQL clause, connect_by, to query
these structures. Oracle also provides pseudo columns for the connect_by meta data,
such as levels, path, isleaf, cycle options, etc. The connect_by functionality with
Microsoft SQL Server (see Reference below) is done natively with a "with" clause or
via custom procedures. SQL Server does not provide any pseudo columns functionality.
Also, SQL Server does not support any analytic and aggregate func
View Complete Post