By Bill Ramos and Vishal Soni, Advaiya Inc.

This blog post covers some of the reasons why SQL Server Migration Assistant (SSMA) for Oracle cannot convert a statement that contains reference to an Oracle SEQUENCE object. A SEQUENCE is an Oracle object that is used to generate an ordered number sequence. This is useful when users need to create a unique number to act as a primary key or foreign key in any table.

Error O2SS0188 Sequence not found in source metadata

Background

To assist in the migration, SSMA can emulate most of the Oracle SEQUENCE behaviors.  In SSMA for Oracle, SEQUENCE emulation is implemented by using both the Transact-SQL procedures and functions, and extended stored procedures.

When converting the sequence, SSMA uses two additional objects in the target SQL Server schema:

1.     A Table named $SSMA_seq_<sq>, that has a single identity column

2.     A Stored procedure $$SSMA_sp_get_nextval_<sq>

SSMA displays the error “O2SS0188 sequence not found in source metadata” if it is not able to locate the sequence object in the SSMA source metadata for the project.

For more information on how SSMA implements the Oracle sequence object, please see the article from DBBest titled Migration of Oracle sequences to SQL Server 2005/ 2008

Reasons

There are two possibilities leading to the scenario where SSMA is not able to find the sequence in the source metadata:

·         The SEQUENCE object was excluded from the import operation when connecting to the Oracle database.

·         The SEQUENCE object is located on a remote database by using a database link.

Possible Remedies

The corresponding sequence was not found in the source metadata. This might happen due to some security features in Oracle or some issues while connecting with the Oracle database. To resolve this, you need to ensure the following:

-          The SSMA is properly connected with the Oracle database and all the Objects from the Oracle database like Triggers, Procedures, and particularly Sequences are visible under the Oracle Metadata Explorer.

Consider the following example:

INSERTINTO employees (employeeid, lastname, Firstname) VALUES(sq1.nextval, 'David', 'Miller');

Here, this query refers to the sequence sq1 created in Oracle, which SSMA will try to migrate to SQL server. But if this SSMA is not able to find the reference of this sequence, it should give the following error:

In this case, make sure that the SSMA is properly linked with the Oracle Database, by referring the Oracle Metadata Explorer. If the corresponding required Sequence is not visible in the Metadata explorer node for Sequences, reconnect with the Oracle with DBA permissions. The referred Sequence should then be visible under the Oracle Metadata explorer.

If the SEQUENCE that you are referencing is in another database using a database link, SSMA doesn’t support the direct migration of the sequence for shared use in SQL Server. Instead, recreate the SEQUENCE on the source database, remove the database link reference in the query, and then use SSMA to convert the SEQUENCE into the SQL Server database.

Related Errors

There are several other errors related to the SEQUENCE that you may encounter. These include the following:

·         O2SS0214 Column has bound sequence, but sequence was not found in source metadata

·         O2SS0216 Call to identity sequence CURRVAL not supported

·         O2SS0221 Call to identity sequence NEXTVAL not supported

References

For more information, check out the following references:

Migrating Oracle to SQL Server 2008 White Paper

CREATE SEQUENCE – Oracle Database SQL Language Reference 11g Release

Migration of Oracle sequences to SQL Server 2005/ 2008

By Bill Ramos and Ankit Matta, Advaiya Inc.

This blog post covers the reasons why SQL Server Migration Assistant (SSMA) for Oracle Cannot Convert Standalone User-Defined Types.

A User Defined Type (UDT) is an entitled data type that is made in the database by the user. A UDT can be a distinct type which segments a common representation with a built-in data type.

Error O2SS0339 Cannot Convert Standalone User-Defined Types

Background

Whenever you create a User Defined data type and make a reference of that data type in a packaged query to declare a variable, SSMA does not recognize this data type and hence does not convert it to corresponding SQL Server code. This is because the user defined data type is not defined in the scope of the code where the variable is being declared and hence generates error “Error O2SS0339 Cannot Convert Usage of Standalone User-Defined Types”

Possible Remedies

Consider the below example, where we have created two different UDTs and then created a package specification followed by a package body. These UDTs are used to declare variables in the package code.

CREATEORREPLACETYPE TO_TEXT ASOBJECT(Text_Id NUMBER, Line NUMBER, Text VARCHAR2(2000))

CREATEORREPLACETYPE TT_TEXT ASTABLEOF To_Text

CREATEORREPLACEPACKAGE PKG_UDTVAR_TEST IS

  g_Text  Tt_Text;

END PKG_UDTVAR_TEST;

CREATEORREPLACEPACKAGEBODY PKG_UDTVAR_TEST IS

BEGIN

  g_Text:=Tt_Text();

END PKG_UDTVAR_TEST;

The solution of the above error is to rewrite the code in Oracle. Just create the user defined data types inside the package specification keeping the remaining code as is.

When you define the UDTs inside the package specification, the UDTs comes in the scope of the Package and hence the error is resolved.

CREATEORREPLACEPACKAGE PKG_UDTVAR_TEST IS

TYPE TO_TEXT IS RECORD (Text_Id NUMBER, Line NUMBER, Text VARCHAR2(2000));

TYPE TT_TEXT ISTABLEOF TO_TEXT;

      g_Text  Tt_Text;

END PKG_UDTVAR_TEST;

/

CREATEORREPLACEPACKAGEBODY PKG_UDTVAR_TEST IS

BEGIN

  g_Text:=Tt_Text();

END PKG_UDTVAR_TEST;

/

Corresponding SQL Server code generated by SSMA

CREATEPROCEDURE dbo.PKG_UDTVAR_TEST$SSMA_Initialize_Package

AS

   DECLARE

     @CollectionIndexInt$TYPE varchar(max) = ' TABLE OF ( RECORD ( TEXT_ID DOUBLE , LINE DOUBLE , TEXT STRING ) )'

   EXECUTE sysdb.ssma_oracle.db_clean_storage

   DECLARE

      @g_Text dbo.CollectionIndexInt

   EXECUTE sysdb.ssma_oracle.set_pv_collection_int

      'PROSEWARE',

      'DBO',

      'PKG_UDTVAR_TEST',

      'G_TEXT',

      @g_Text

   DECLARE

      @temp dbo.CollectionIndexInt

      SET @temp = dbo.CollectionIndexInt ::[Null].SetType(@CollectionIndexInt$TYPE)

      EXECUTE sysdb.ssma_oracle.set_pv_collection_int

      'PROSEWARE',

      'DBO',

      'PKG_UDTVAR_TEST',

      'G_TEXT',

      @temp

GO

Related Errors

There are several other errors related to “User defined Types” that you may encounter. These include the following:

·         Emulating Records and Collections using CLR UDTs

References

For more information, check out the following references:

Migrating Oracle to SQL Server 2008 White Paper

SSMA Blog: Converting Oracle UDT to SQL Server TVP

By Bill Ramos and Badal Bordia, Advaiya Inc.

This blog post describes why SQL Server Migration Assistant (SSMA) for Oracle doesn’t convert the PL/SQL block when package variable holds an unsupported datatype such as INTERVAL datatype.

In Oracle INTERVAL datatype defines a period of time that specifies the difference in terms of years and months, or in terms of days, hours, minutes, and seconds.

Error O2SS0350 Conversion of packaged variable (constant) data type is not supported in this release

Background

Whenever package variable holds an INTERVAL data type or any other datatype that is unsupported by SSMA, it generate following error: ‘Error O2SS0350 Conversion of packaged variable (constant) data type is not supported in this release’

Possible Remedies

Consider the example below, where we have created a package that contains an INTERVAL data type.

CREATEORREPLACEPACKAGE PKG_VAR_TEST IS

start_d date;

end_d date;

v_interval INTERVALYEAR(1) TOMONTH;

i_year NUMBER;

i_month NUMBER;

END PKG_VAR_TEST;

/

CREATEORREPLACEPACKAGEBODY PKG_VAR_TEST is

Begin

  start_d := to_date('12-sep-2004', 'dd-mon-yyyy');

  end_d := to_date('12-sep-2009', 'dd-mon-yyyy');

  v_interval := (end_d - start_d) YEARTOMONTH;

  i_year := extract(YEARFROM v_interval);

  i_month := extract(MONTHFROM v_interval);

  dbms_output.put_line('year: ' || i_year);

  dbms_output.put_line('month: ' || i_month);

END PKG_VAR_TEST;

/

When SSMA tries to convert the above code, it generates following error: ‘Error O2SS0350 Conversion of packaged variable (constant) data type is not supported in this release’.

The solution of the above problem error is to use ‘DATEDIFF’ function in SQL Server. ‘DATEDIFF’ function returns the number of date and time boundaries crossed between two specified dates. For this, we need to update the SQL Server code as follows:

CREATEPROCEDURE dbo.PKG_VAR_TEST$SSMA_Initialize_Package_new

AS

   EXECUTE sysdb.ssma_oracle.db_clean_storage

   DECLARE

      @temp datetime2

   SET @temp = sysdb.ssma_oracle.to_date2('12-05-2004', 'dd-mm-yyyy')

   EXECUTE sysdb.ssma_oracle.set_pv_datetime2

      'PROSEWARE',

      'DBO',

      'PKG_VAR_TEST',

      'START_D',

      @temp

   DECLARE

      @temp$2 datetime2

   SET @temp$2 = sysdb.ssma_oracle.to_date2('01-09-2009', 'dd-mm-yyyy')

   EXECUTE sysdb.ssma_oracle.set_pv_datetime2

      'PROSEWARE',

      'DBO',

      'PKG_VAR_TEST',

      'END_D',

      @temp$2

   PRINT( ( right('00' +

rtrim(ltrim(str(DATEDIFF(yy,@temp, @temp$2)))),2) + ':' +

right('00' +

rtrim(ltrim(str(DATEDIFF(MM,@temp, @temp$2)%12))),2)))

GO

Exec dbo.PKG_VAR_TEST$SSMA_Initialize_Package_new;

References

For more information, check out the following references:

·         Migrating Oracle to SQL Server 2008 White Paper

By Bill Ramos and Badal Bordia, Advaiya Inc.

This blog post describes why SQL Server Migration Assistant (SSMA) for Oracle doesn’t support the conversion of some of the collection method

A collection is an ordered group of elements, all of the same type. It is a general concept that encompasses lists, arrays, and other familiar data types. You can use the methods EXISTS, COUNT, LIMIT, FIRST, LAST, PRIOR, NEXT, EXTEND, TRIM, and DELETE to manage collections in Oracle whose size is unknown or varies.

Error O2SS0351   Conversion of collection method not supported

Background

Whenever you make a reference of Limit method in collection query, SSMA is not able to resolve that method. Hence, usage of this collection method results in error O2SS0351  In Oracle, LIMIT returns the maximum number of elements that array can contain (which you must specify in its type definition).

Possible Remedies

Consider the below example:

DECLARE

      TYPE VARRAYTEST ISVARRAY(5) OFVARCHAR2(25);

      vTest VARRAYTEST;

BEGIN

      vTest := VARRAYTEST('text1', 'text2', 'text3');

      DBMS_OUTPUT.PUT_LINE('COLLECTION LIMIT IS -- ' || vTest.LIMIT);     

END;

When SSMA tries to convert the above code, it gives the error “Error O2SS0351   Conversion of collection method not supported”.

The solution of the above error is to modify the code in SQL Server because LIMIT method is not relevant in the way SSMA emulates the collection.  When SSMA converts the array collection element of Oracle to SQL Server, it allocates the maximum size to the collection element and SQL server allows dynamic allocation to the collection at the run time.

So for the above example, we have replaced the Limit method with Count method of SQL server to get the number of elements in collection

BEGIN

   DECLARE

      @CollectionIndexInt$TYPE varchar(max)=' VARRAY OF STRING',

      @vTest dbo.CollectionIndexInt

      SET @vTest = dbo.CollectionIndexInt    

::[Null].SetType(@CollectionIndexInt$TYPE).AddString('text1').AddString('text2').AddString('text3')

      PRINT'COLLECTION LIMIT IS -- '+ISNULL(CAST(@vTest.CountAS

nvarchar(max)),'')

END

Related Errors

There are several other errors related to “Collection conversion“ that you may encounter. These include the following:

·         Error O2SS0408 Collection or Record Type is not supported

·         Error O2SS0316: Conversion of collection element not supported

·         Error O2SS0323: Conversion of collection method not supported

References

For more information, check out the following references:

·         Migrating Oracle to SQL Server 2008 White Paper

Automating Database Migration to SQL Server 2012

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

• Support conversion of Oracle %ROWTYPE parameters with NULL default
• Support conversion of Sybase’s Rollback Trigger
• Better user credential security to support Microsoft Access Linked Tables

Download SQL Server Migration Assistant (SSMA) v.5.2

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.

SSMA simplifies database migration process from Oracle/Sybase/MySQL and Microsoft Access to SQL Server and SQL Azure. SSMA automates all aspects of migration including migration assessment analysis, schema and SQL statement conversion, data migration as well as migration testing to reduce cost and reduce risk of your database migration project. 

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

SSMA simplifies database migration process from Oracle/Sybase/MySQL and Microsoft Access to SQL Server and SQL Azure. SSMA automates all aspects of migration including migration assessment analysis, schema and SQL statement conversion, data migration as well as migration testing to reduce cost and reduce risk of your database migration project. 

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:  http://www.microsoft.com/en-us/download/details.aspx?id=43690

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

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

SSMA for Sybase: http://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

Microsoft Access stores all the connection strings for the respective linked tables in a system table called MSysObjects.  As seen below, the connection strings contain clear-text used id and password.  With the release for SSMA for Access 5.2, when creating link tables during migration, users will now have the option to not store the user id and password for the linked tables.

A new setting for linked tables can be found under the Project Settings menu.    By default, the Store user credentials setting is set to false, thus user id and password will not be persisted in the connection string of a linked table.  Switching the setting to true would provide the option to store the user id and password in the connection strings during the creation of linked tables.

It is important to note that after securing the connection string, MS Access users will have to enter the required user id and password whenever the linked tables are referenced in the MS Access Database application.  Below shows the prompt presented by MS Access.

The %ROWTYPE attribute in Oracle defines the particular record type of a row in a table.   A common usage of %ROWTYPE attribute is to have variables declared as ROWTYPE of a table to transfer data in and out of a procedure or function.  An IN ROWTYPE parameter of a function or procedure can be set with a default value.  Often, the IN ROWTYPE parameter is defaulted to NULL.  For example,

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 

Unfortunately we never had Sybase ASA on our plans for SSMA. The plan is still intact and we still support migration from Sybase ASE 11.9 onwards with the latest version of SSMA for Sybase http://www.microsoft.com/en-us/download/details.aspx?id=28765

 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 :  http://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 : http://social.msdn.microsoft.com/Forums/en-US/sqldataaccess/thread/fe29f12d-67b0-40a8-a41b-1767853a0185

Angshuman Nayak 

SSMA simplifies database migration process from Oracle/Sybase/MySQL and Microsoft Access to SQL Server and SQL Azure. SSMA automates all aspects of migration including migration assessment analysis, schema and SQL statement conversion, data migration as well as migration testing to reduce cost and reduce risk of your database migration project. 

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

SSMA simplifies database migration process from Oracle/Sybase/MySQL and Microsoft Access to SQL Server and SQL Azure. SSMA automates all aspects of migration including migration assessment analysis, schema and SQL statement conversion, data migration as well as migration testing to reduce cost and reduce risk of your database migration project. 

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:  http://www.microsoft.com/en-us/download/details.aspx?id=43690

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

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

SSMA for Sybase: http://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

We are happy to announce the release of the most anticipated DB2 for SSMA. You can download the same from the link : http://www.microsoft.com/en-us/download/details.aspx?id=45296

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

Microsoft has released an update to SSMA 6.0 for Oracle, DB2, Sybase ASE, MySQL and Access. SSMA simplifies the database migration process by automating all aspects of migration including migration assessment analysis, schema conversion, SQL statement conversion and data migration. SSMA also includes migration testing to reduce the cost and risk of database migrations.

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:    http://www.microsoft.com/en-us/download/details.aspx?id=51214
• SSMA 6.0.1 for DB2:        http://www.microsoft.com/en-us/download/details.aspx?id=51216
• SSMA 6.0.1 for MySql:     http://www.microsoft.com/en-us/download/details.aspx?id=51218
• SSMA 6.0.1 for Oracle:    http://www.microsoft.com/en-us/download/details.aspx?id=51217
• SSMA 6.0.1 for Sybase:   http://www.microsoft.com/en-us/download/details.aspx?id=51215

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

Microsoft has released a preview release of SQL Server Migration Assistant (SSMA) that supports migrating databases from Oracle, Sybase ASE, DB2, MySQL and Access to SQL Server 2016 Release Candidate 0. In this release, the following features have been added:

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: http://www.microsoft.com/en-us/download/details.aspx?id=51472
• Oracle: https://www.microsoft.com/en-us/download/details.aspx?id=51471
• Access: http://www.microsoft.com/en-us/download/details.aspx?id=51473
• MySql: http://www.microsoft.com/en-us/download/details.aspx?id=51470
• DB2: http://www.microsoft.com/en-us/download/details.aspx?id=51469

Microsoft has released SQL Server Migration Assistant (SSMA) 7.0 which now supports migrating to SQL Server 2016 and has expanded support for Azure SQL Database.

All platforms:

• 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

To download the SSMA 7.0 release see the following links:

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

SQL vNext CTP1 on Windows and Linux is now a supported target platform for migration. This feature is in technical preview and will allow schema and data movement to the target SQL server.
Review the announcement here.

Overview

Microsoft SQL Server Migration Assistant (SSMA) v7.3  for Oracle, MySQL, SAP ASE (formerly SAP Sybase ASE), DB2 and Access lets users convert database schema to Microsoft SQL Server schema, upload the schema, and migrate data to the target SQL Server (see below for supported versions).

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

NOTE: Please visit https://blogs.msdn.microsoft.com/datamigration/  for latest post on tools that support upgrades and migrations.