The story goes that Willy Sutton robbed banks because "that's where the money is." While this attribution appears to be an urban legend, it's no myth that Oracle has a lion's share of databases - both transactional and analytic.
IBM started an advanced land grab for Oracle customer conversions by bringing a high compatibility of PL/SQL into the DB2 database.
Now, Teradata has invested resources in facilitating the migration away from Oracle. With the Teradata Migration Accelerator (TMA). structure and SQL (PL/SQL) code can be converted to Teradata structures and code. This is a different philosophy from IBM, which requires few code changes for the move, but also doesn't immediately optimize that code for DB2.
While data definition language (DDL) has only minor changes from DBMS to DBMS, such as putting quotes around keywords, Teradata's key activity and opportunity in the migration is to change Oracle cursors to Teradata set-based SQL.
"Rule sets" - for how to do conversions - can be applied selectivity across the structure and code in the migration. TMA supports selective data movement, if desired, with WHERE clauses for the data. TMA also supports multiple users doing a coordinated migration effort.
TMA also works for DB2 migrations.
While it will not do the trick on its own, having these tools, which convinces a shop that the move could be more pain-free than originally thought, will support DBMS migrations.
Posted April 30, 2012 10:15 AM
Permalink | No Comments |