1. TechReady13 Dmitry Balin DB Best Technologies
9/17/2018
Peace of mind: Quick Tour through the New SQL server Migration Assistant (SSMA)
Dmitry Balin
DB Best Technologies
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Session Objectives and Takeaways
TechReady13
9/17/2018
Session Objectives and Takeaways
Why Migrate to SQL Server
Database and Application Migration Process
SQL Server Migration Assistant (SSMA)
Database Migration Challenges
Migration Best Practices
Resources
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Why Migrate to SQL Server
Why Migrate from Oracle to Microsoft SQL Server?
Why Migrate to SQL Server
What some of our customers say …
We moved nine-terabyte system migrated from Oracle using SSMA that resulted in significant TCO savings.
We were going for Better - Faster - Cheaper. And we attained all three!
We not only reduced annual licensing costs but we also improved uptime.
We improved development productivity and lowered cost after migrating our mission-critical system from Oracle.
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

4. Database and Application Migration Process
Scoping and Planning
Microsoft Assessment
and Planning Toolkit
Database Discovery
Non-code requirements (HADR, Perf, locale, maintenance, dependencies, etc.)
Database Migration
Migration Assistant
Migration Impact Assessment
Schema Conversion
Data Migration
Embedded SQL Statements
Application Conversion
Application Deployment
Database connectivity
User Login and Permission

5. Demo
SQL Server Migration Assistant

6. SQL Server Migration Assistant
Automates and simplifies all phases of database migration
Assess migration complexity
Migration Analyzer
Convert schema and business logic
Schema Converter
Migrate data
Data Migrator
Validate converted database code
Migration Tester
Support migration from Oracle, Sybase, MySQL and Access databases to SQL Server

7. Database Migration Challenges
Feature and dialect differences requires non-direct mapping and emulation
Oracle
SQL Server
Table/View
Table/View
Data Types
Data Types
Procedure
T-SQL
Procedure
User Db
User Function
User Defined Function
Package
Sequence
Trigger
Trigger
System Function
SysDb
System Function
Emulator
Standard Package
Master
PL/SQL

8. Demo
A Closer Look at Schema Conversion

9. What’s New in SSMA SSMA 5.0 SSMA 5.1 Migration to SQL Server 2012
Multi-thread data migration
Globalization support
Oracle User Defined Type discovery
Sybase migration enhancements
Support for conversion of Oracle sequence to SQL Server 2012 sequence generator
Support for conversion of LIMIT to SQL Server 2012 OFFSET/FETCH NEXT
Improved error reporting during data migration

10. Migration Best Practices
Customize SSMA project settings
65 configuration options for Oracle Migration
55 configuration options for Sybase Migration
65 configuration options for MySQL Migration
25 configuration options for Access Migration
Testing and validation
Allocate ~30% of the project effort to testing and validation of the converted code
Use tools (e.g. DB Best Database Compare Suite) to validate schema and data conversion
Performance testing and benchmarking is key metrics for project success
Application conversion
Analyze and identify all applications interfacing with the Oracle database
Look for embedded SQL statements spread across the application code
Optimize infrastructure, people and processes
Server, storage, security, maintenance, monitoring, troubleshooting
Advanced level training/workshops

11. Resources
Database Migration Resources & Whitepaper
Free Technical Product support (FREE technical support from Microsoft CSS)
Discussion Forums
SSMA Team Blog
Additional migration resources and tools

12. Further. Forward. Faster.
Learn more Visit the Microsoft Virtual Academy Free technical SQL Server training courses
Get more Download SQL Server 2012 Trial Software 180-day evaluation of SQL Server 2012
Do more Participate in virtual launch activities and collect points for prizes The more points you earn, the bigger your prize could be

13. Appendix

14. Converting Data Types Migration Challenges SSMA Conversion Approach
Dynamic precision and scale
NUMBER, VARCHAR2
Wider range of supported value
Oracle stores from 4712 while SQL Server’s DATETIME stores from 01/01/1753 and DATETIME2 stores from 01/01/0001
TIMESTAMP has nanosecond precision while DATETIME2 stores up to 100 nanoseconds
Complex data type
User defined type: Object type, collections
SSMA Conversion Approach
Convert to maximum possible
NUMBER converted to float(53), which has the maximum precision from SQL Server floating-point numbers
VARCHAR2 converted to VARCHAR(MAX)
Project setting
specify how to handle out of bound values during data migration
Error, null, closest supported value
Raise conversion message when user defined type is used in table, view, and PL/SQL program

15. Converting Procedures and Functions
Migration Challenge
No big differences between procedure and function in Oracle
error handling
DML statement: update, insert, delete
temporary table access
calling procedures (except extended procedures)
Parameter
Support IN, OUT and IN OUT parameters
Scale and precision not specified
Parameter overloading
Procedures don’t return result sets
Use cursors, records and collection as output parameter
Autonomous Transaction
SSMA Conversion Approach
Functions converted to function and stored procedure when containing operations forbidden in functions are needed
such procedures have $IMPL suffix
Extended stored procedure to call procedure within function and emulate autonomous transaction
master..xp_ora2ms_exec2

16. Converting Oracle Packages
SSMA Conversion Approach
Convert to procedure and function with the following naming convention
dbo.PACKAGENAME$MODULENAME
Emulate package variable by storing values in a central table
Inline substitution for module nesting
Migration Challenge
Oracle specific implementation to logically group schema objects
Compare to SQL Server’s Schema:
No concept of global package objects
Variables and constants
No concepts of private/public objects
Private functions, procedures, types
No concept of package state
E.g. invalid because of compilation errors
Module nesting
Definition of procedures/functions
Inside other modules

17. Converting Oracle Sequences
Migration Challenge
Generate number sequence – not bound to a table
NEXTVAL method to generate next value of a sequence
CURRVAL method to retrieve current value of the sequence (bound to current session scope)
SSMA Conversion Approach
One table per sequence
Uses IDENTITY
Get values through procedures/functions
Maintenance
Additional procedures to drop/create
Limitation
Min/max values are not enforced
Functions are slower
Use extended stored procedure to exec procedure
Some options not available
NOCYCLE, NOCACHE, NOORDER

18. Converting Oracle Triggers
Migration Challenge
FOR EACH ROW trigger
The most common Oracle trigger which fires for each row of the source statement.
SQL Server only supports statement level trigger
Before trigger
Possible to modify the actual field values that will be stored in the table, or even cancel the execution
Allow multiple trigger for each events (INSERT or UPDATE)
SQL Server only supports one trigger per event
SSMA Conversion Approach
Row-level triggers are emulated with a cursor loop and generate ROWID for table with trigger.
BEFORE triggers are converted to INSTEAD OF trigger
Incorporate triggering statement into the trigger body
Cursor loop to handle affected multiple rows
Logic from all BEFORE triggers on that table into a single target trigger.

19. SSMA 5.0 Sybase Migration Enhancements
Support for migration to SQL Azure.
Extended data access connectivity to Sybase ASE ADO.NET and ASE ODBC providers.
Support for conversion of case sensitive Sybase database to case sensitive SQL Server.
Extended support for conversion of Non-ANSI joins for DELETE and UPDATE statements.
Removed dependency on separate SYSDB database on target SQL Server.

20. TechReady13
9/17/2018
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.