What is new in v7.3?

• Improved quality and conversion metric with targeted fixes based on customer feedback.
• SSMA extensibility framework exposed via
  • Export functionality to a SQL Server Data Tools (SSDT) project
    • You can now export schema scripts from SSMA as an SSDT project and use that to make additional schema changes and deploy your database.
  • Libraries that can be consumed by SSMA for performing custom conversions
    • You can now construct code that can handle custom syntax conversions and conversions that weren't previously handled by SSMA
      • Instructions on how to construct a custom converter can be found here.
      • Sample project for conversion can be downloaded here.

Downloads

• SSMA for Access
• SSMA for DB2
• SSMA for MySQL
• SSMA for Oracle
• SSMA for SAP ASE (formerly SAP Sybase ASE)

Resources

• SQL Server Migration Assistant: How to assess and migrate database(s) from non Microsoft data platforms to SQL Server
• Extending SQL Server Migration Assistant's conversion capabilities

• Support for SQL Server 2016
• Extended support for Azure SQL Database
• Support for running SSMA on Windows 10
• Fixed "save project" and "open project" commands for SSMA Console
• Fixed "securepassword" command for SSMA Console
• Fixed counting of objects for initial loading
• Removed installer check for .Net 2.0

Oracle

• Add conversion for in-memory tables and column store indexes to leverage In-Memory OLTP for SQL Server 2016 and In-Memory Columnstore for SQL Server 2016 and Azure SQL Database
• Added conversion of Oracle flashback archive tables to leverage SQL Server Temporal tables in SQL Server 2016 and Azure SQL Database
• Added conversion of Oracle VPD Policy converting to leverage Row Level Security in SQL Server 2016 and Azure SQL Database
• Decreased time of initial loading for Oracle
• Improved parser and resolver
• Updated Extension Pack dependency from .Net 3.5 to .Net 4.0

Db2

• Added conversion of DB2 in-memory tables and column store indexes to leverage In-memory OLTP for SQL Server 2016 and In-Memory Columnstore for SQL Server 2016 and Azure SQL Database
• Added conversion of DB2 access controls to leverage SQL Server Row Level Security for SQL Server 2016 and Azure SQL Database
• Added conversion of DB2 system-versioned tables to leverage SQL Server Temporal tables for SQL Server 2016 and Azure SQL Database
• Improved DB2 parser and resolver
• Removed unnecessary *.dll from Db2 installer

MySQL

• Improved parser and resolver
• Updated Extension Pack dependency from .Net 3.5 to .Net 4.0
• Fixed default BigInt typemapping for MySQL
• Fixed MsSql objects loading

MS Access

• Fixed tables data loading for UI tabs for Access
• Added support for disabling the loading of linked tables

Sybase ASE

• Updated Extension Pack dependency from .Net 3.5 to .Net 4.0

• SSMA for MS Access
• SSMA for DB2
• SSMA for MySQL
• SSMA for Oracle
• SSMA for Sybase ASE

SSMA 6.1 Preview, all platforms:

• Support for SQL Server 2016 Release Candidate 0
• Support for running SSMA on Windows 10

SSMA 6.1 Preview for Oracle now supports Row Level Security including the following:

• Support loading of security policies from the Oracle Virtual Private Database (VPD)
• The Oracle VPD is represented in the SSMA UI with policy objects underneath
• The associated VPD attributes and predicate function are represented in the SSMA UI
• Support loading of security policies from SQL Server 2016
• SQL Server Security policies are represented in the SSMA UI and organized in categories
• The SQL Server Security policies associated attributes are represented in the SSMA UI
• Support for conversion of Oracle security policies to SQL Server security policies

SSMA 6.1 Preview for Oracle now supports In-Memory Tables and Column Store including the following:

• Support loading of in-memory tables shown in UI with 'M' icon
• Support conversion to selected SQL Server mapping:
  • Row-store table with Non-clustered Columnstore Index
  • In-memory OLTP tables
  • Clustered Columnstore Index-organized table
  • Row-store table without Columnstore Indexes

To download the SSMA 6.1 Preview release see the following links:

• Sybase ASE: https://www.microsoft.com/en-us/download/details.aspx?id=51472
• Oracle: https://www.microsoft.com/en-us/download/details.aspx?id=51471
• Access: https://www.microsoft.com/en-us/download/details.aspx?id=51473
• MySql: https://www.microsoft.com/en-us/download/details.aspx?id=51470
• DB2: https://www.microsoft.com/en-us/download/details.aspx?id=51469

Version 6.01 of SSMA includes the following enhancements:

• SSMA for Oracle.
• Added support for clustered indexes.
• Fixed performance with querying Oracle schema. 
• Fixed issues when setting up a connection to Azure from the console.
• SSMA for DB2.
• Fixed support for DB2 v9 zOS.
• Added support for more standard functions.
• Fixed issues when setting up a connection to Azure from the console.
• SSMA for MySQL.
• Updated driver support now includes newer versions of the ODBC driver greater than v5.1.
• SSMA for Access.
• Fixed handing of fields with a GUID datatype and a default function.
• Fixed issues importing records into an Azure SQL Database.
• New command in the menu to view the SSMA log file.
• This provides an easy way to get to the log file to help diagnose any issues that come up when using SSMA.

 Download SQL Server Migration Assistant (SSMA) v6.0.1

• SSMA 6.0.1 for Access:    https://www.microsoft.com/en-us/download/details.aspx?id=51214
• SSMA 6.0.1 for DB2:        https://www.microsoft.com/en-us/download/details.aspx?id=51216
• SSMA 6.0.1 for MySql:     https://www.microsoft.com/en-us/download/details.aspx?id=51218
• SSMA 6.0.1 for Oracle:    https://www.microsoft.com/en-us/download/details.aspx?id=51217
• SSMA 6.0.1 for Sybase:   https://www.microsoft.com/en-us/download/details.aspx?id=51215

For help and support using SSMA, please visit https://aka.ms/ssmahelp.

We look forward to hear back from your end on the feedback related to the utility.

The new version of  SSMA, Version  6.0 provides the following major enhancements:

• Materialized View support for Oracle

• Memory Optimized tables for Oracle
• Improved Azure SQL DB code conversion
• Extension pack functionality moved to schema to support Azure SQL DB
• Performance improvements tested for databases with over 10k objects
• UI improvements for dealing with large number of objects
• Highlighting of “well known” LOB schemas (so they can be ignored in conversion)
• Conversion speed improvements
• Show object counts in UI
• Report size reduction by more than 25%
• Improved error messages for unparsed constructs.

 Download SQL Server Migration Assistant (SSMA) v.6.0

SSMA for Access:  https://www.microsoft.com/en-us/download/details.aspx?id=43690

SSMA for MySQL: https://www.microsoft.com/en-us/download/details.aspx?id=43688

SSMA for Oracle:  https://www.microsoft.com/en-us/download/details.aspx?id=43689

SSMA for Sybase: https://www.microsoft.com/en-us/download/details.aspx?id=43691

On the closing note , Yes ! We've heard several of your valuable feedbacks / inputs. Thank you... and we're rolling out with the SSMA for DB2 very soon. Watch out this space for more information.

The SSMA product team is available to answer your questions and provide technical support related to SSMA. Contact the team at ssmahelp@microsoft.com

The new version of SSMA - SSMA 5.3 provides the following major enhancements:

• Support of Migration to MS SQL Server 2014.
• Improved conversion mechanism when migrating to Azure.
• New features in the Migration GUI.
• No requirement to get a License key to start using SSMA.

Download SQL Server Migration Assistant (SSMA) v.5.3 :

Launch the download of the SSMA for Oracle.

Launch the download of the SSMA for Sybase.

Launch the download of the SSMA for MySQL.

Launch the download of the SSMA for Access.

The SSMA product team is available to answer your questions and provide limited technical support. Contact the team at ssmahelp@microsoft.com

 Even if we can’t use SSMA we still have a way to migrate in case only schema and data needs to be migrated (which is mostly the case). You can use a Linked Server to great advantage. The syntax between Sybase and MS SQL Server don’t differ much as they share the same DNA. Below are the providers that you can use to setup a linked server from SQL Server to Sybase ASA and then use queries to pull data and insert into the local database.  I am providing some information below to give you pointers for the same.   

a)      Have to install the required provider/driver on the SQL Server machine.

 Sybase ASA can be connected in following ways

 OLE DB Providers

 You need an OLE DB provider for each type of data source you wish to access. Each provider is a dynamic-link library. There are two OLE DB providers you can use to access Sybase IQ:  Sybase ASA OLE DB provider The Adaptive Server Anywhere OLE DB provider provides access to Sybase IQ as an OLE DB data source without the need for ODBC components. The short name for this provider is ASAProv. 

When the ASAProv provider is installed, it registers itself. This registration process includes making registry entries in the COM section of the registry, so that ADO can locate the DLL when the ASAProv provider is called. If you change the location of your DLL, you must reregister it. 

If you use the Adaptive Server Anywhere OLE DB provider, ODBC is not required in your deployment. 

ODBC Driver

Microsoft OLE DB provider for ODBC Microsoft provides an OLE DB provider with a short name of MSDASQL.

The MSDASQL provider makes ODBC data sources appear as OLE DB data sources. It requires the Sybase IQ ODBC driver.

 b)      Create a Linked Server and then query the same.

 This link species the steps and some common errors while setting the Sybase ASA Linked Server

 Steps :  https://sql-articles.com/articles/dba/creating-linked-server-to-sybase-from-sql-server/  (These are for ASE but are the same for ASA except that you have to choose a different provider/driver)

 Connection Issues : https://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/fe29f12d-67b0-40a8-a41b-1767853a0185

Angshuman Nayak 

PROCEDURE proc_foo_rowtype( 
 row_a employees%ROWTYPE DEFAULT NULL ) 
 IS 
BEGIN 
 DBMS_OUTPUT.PUT_LINE('ID = ' || NVL(TO_CHAR(row_a.employeeID), 'NULL')); 
 DBMS_OUTPUT.PUT_LINE('NAME = ' || NVL(TO_CHAR(row_a.firstName), 'NULL')); 
END proc_foo_rowtype; 
 

PROCEDURE dbo.PROC_FOO_ROWTYPE 
 @row_a$EMPLOYEEID float(53) = NULL, 
 @row_a$FIRSTNAME nvarchar(max) = NULL 
AS 
BEGIN 
 PRINT 'ID = ' + isnull(CAST(@row_a$EMPLOYEEID AS varchar(max)), 'NULL') 
 PRINT 'NAME = ' + isnull(CAST(@row_a$FIRSTNAME AS varchar(max)), 'NULL') 
END 

Now, let’s have a little fun by having a ROWTYPE parameter in a nested procedure.  Here’s an example:

PROCEDURE PROC_FOO_OUTER 
IS 
empRow employees%ROWTYPE; 

 procedure proc_foo_inner( 
 row_a IN employees%ROWTYPE default null) 
 IS 
 
 BEGIN 
 DBMS_OUTPUT.PUT_LINE(‘First name = ' || NVL(TO_CHAR(row_a.FirstName), 'NULL')); 
 DBMS_OUTPUT.PUT_LINE(‘Last Name = ' || NVL(TO_CHAR(row_a.LastName), 'NULL')); 
 END proc_foo_inner; 

BEGIN 
 empRow.LastName := 'Smith'; 
 empRow.FirstName := 'John'; 
 proc_foo_inner(); 
 proc_foo_inner(empRow); 

END PROC_FOO_OUTER;                          

This example is quite straightforward.    Let’s assume there is an employee table with FirstName and LastName columns of nvarchar2(20) and nvarchar2(40) respectively.   The executing this procedure in Oracle would the following result:

 Now, let’s convert this procedure to SQL Server 2012 using SSMA for Oracle.  We will set the following settings in SSMA as such

• ·         local modules conversion is set to Inline
• ·         convert record as a list of separated variables set to Yes

The first setting is to convert the inner procedure into nested block Begin..End.  The second setting will create separate variables for FirstName and LastName.

Below is the result of the conversion.  There are two nested blocks corresponding to the respective inner procedures.  Each nested block contains its own variables for LastName and FirstName.   For the block representing proc_foo_inner(), the two variables are set to NULL.  For the block representing proc_foo_inner(empRow), the variables are set to the proper empRow values.

PROCEDURE dbo.PROC_FOO_OUTER 
AS 
 BEGIN 
 
 DECLARE 
 @empRow$LASTNAME nvarchar(40), 
 @empRow$FIRSTNAME nvarchar(20), 
 
 
 SET @empRow$LASTNAME = 'Smith' 
 SET @empRow$FIRSTNAME = 'John' 
 

 BEGIN /* proc_foo_inner() */ 
  DECLARE 
  @proc_foo_inner$row_a$LASTNAME nvarchar(max) 
 
  DECLARE 
   @proc_foo_inner$row_a$FIRSTNAME nvarchar(max) 
 
   SET @proc_foo_inner$row_a$LASTNAME = NULL 
   SET @proc_foo_inner$row_a$FIRSTNAME = NULL 
 
   BEGIN 
    PRINT 'Last name = ' + isnull(CAST(@proc_foo_inner$row_a$FIRSTNAME AS varchar(max)), 'NULL') 
    PRINT 'First Name = ' + isnull(CAST(@proc_foo_inner$row_a$LASTNAME AS varchar(max)), 'NULL') 
   END 
 END 
 

BEGIN /* proc_foo_inner(empRow) */ 
 DECLARE 
 @proc_foo_inner$row_a$LASTNAME$2 nvarchar(max) 
 
 DECLARE 
 @proc_foo_inner$row_a$FIRSTNAME$2 nvarchar(max) 

 
  SET @proc_foo_inner$row_a$LASTNAME$2 = @empRow$LASTNAME 
  SET @proc_foo_inner$row_a$FIRSTNAME$2 = @empRow$FIRSTNAME 
 
  BEGIN 
   PRINT 'Last name = ' + isnull(CAST(@proc_foo_inner$row_a$FIRSTNAME$2 AS varchar(max)), 'NULL') 
   PRINT 'First Name = ' + isnull(CAST(@proc_foo_inner$row_a$LASTNAME$2 AS varchar(max)), 'NULL') 
  END 
 END 
END