Released: SQL Server Migration Assistant (SSMA) v7.3

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…

0

Preview release of SQL Server Migration Assistant (SSMA) for SQL Server 2016 RC0

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…

4

Microsoft SQL Server Migration Assistant (SSMA) v6.0.1 is now available

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…

8

Latest Update – Microsoft SQL Server Migration Assistant (SSMA) v6.0 is now available.

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,…

24

Microsoft SQL Server Migration Assistant (SSMA) v5.3 is now available.

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 -…

19

Microsoft SQL Server Migration Assistant (SSMA) 5.2 is Now Available

Automating Database Migration to SQL Server 2012 SQL Server Migration Assistant (SSMA) v5.2 is now available. 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…

65

Identifying Database Migration Opportunity Using MAP 6.0

Microsoft announced the release of Microsoft Assessment and Planning (MAP) toolkit 6.0. The new version of MAP reports the existence of Oracle database instances and provides information that can be use to estimate total cost of ownership and return-on-investment (ROI) for migrating the Oracle schema to SQL Server. You can download MAP 6.0 from Microsoft…

0

How SSMA Estimates Manual Conversion Time

SSMA automates conversion of most statement. There are a few features and syntax which SSMA is unable to migrate. In such situation, SSMA issues a migration error and for each error, SSMA provides estimated manual conversion time. I often asked how do we come up with the time. Those manual estimation time was calculated based…

0

Migrating Oracle ANYDATA to SQL Server

By Welly Lee, Pinaki Bag, and Jayakumar Tanneru. Oracle has an object data type called anydata. This data type supports wide range of data types. For example when creating a table with a column defined as anydata type, the column can store many types of data from string to numeric . SSMA does not support…

0

Migrating Oracle to SQL Server using SSMA–Error O2SS0041 Illegal Identifier

When converting Oracle schema to SQL Server using SSMA, you may encounter an error when your table contains a DATE column with default value. This blog post describes the reason for the error and what you should do when you encounter this error. Consider the following example — Oracle source table: CREATE TABLE TEST.T1 (…

0