This blog posting focuses on tasks associated with migrating an Oracle database to the latest version of SQL Server. If preparing for a migration requires changes to Oracle features/functionality, then it is important to carefully consider the potential impact of each change on the applications that use the database. This posting provides links to detail about workaround solutions for migrating specific Oracle features to SQL Server, each providing one or more alternatives. Some methods are quick and easy, while others require greater effort to prepare and test.
The article assumes a reader's familiarity with the database that is being migrated and the applications that use the database, such that the reader is in a position to assess the impact on the applications before and after database migration.
Note: The versions of SQL Server, Visual Studio tools, and SQL Server Migration Assistant (SSMA) described in this document are subject to change, so be sure to download and install the latest versions of the documentation and tools before you begin.
Click the link below on details about how to migrate specific Oracle features that are not supported by SSMA.
The Data Migration Team would like to thank Mohanrao Thotakura (Solution Architect for Oracle migrations) for authoring the Migration Approach document; Parikshit Savjani (SQL Tiger Team), Victor Adeyanju and Tom Mills (Microsoft Field Engineer) for serving as Technical Reviewers.