What's New in SSMA for Sybase (SybaseToSQL)

This topic lists SSMA for Sybase changes in each release.

SSMA v7.4

The v7.4 release of SSMA for Sybase contains the following changes:

  • The Query timeout option is now available during schema object discovery at source and target. query timeout option
  • The quality and conversion metric has been improved with targeted fixes, based on customer feedback.
Important

.Net 4.5.2 is a pre-requisite for installing SSMA v7.4. In addition, beginning with v7.4, the 32-bit version of SSMA is being discontinued.

SSMA v7.3

The v7.3 release of SSMA for Sybase contains the following changes:

  • Improved quality and conversion metric with targeted fixes based on customer feedback.
  • SSMA extensibility framework exposed via the following items:
    • Export functionality to a SQL Server Data Tools (SSDT) project.
      • You can now export schema scripts from SSMA to an SSDT project. You can use the schema scripts to make additional schema changes and deploy your database. Save as SSDT project command
    • Libraries that can be consumed by SSMA for performing custom conversions.

SSMA v7.2

The v7.2 release of SSMA for Sybase contains the following changes:

  • Improved quality and conversion metric with targeted fixes based on customer feedback.
  • Telemetry enhancements to provide better data points to troubleshoot customer issues and improve SSMA’s conversion rates.

SSMA v7.1

The v7.1 release of SSMA for Access contains the following changes:

  • SQL Server 2017 on Windows and Linux CTP1 is now a supported target platform for migration. This feature is in technical preview and supports schema and data movement to target SQL servers.
  • SSMA now supports automatic updates to download the latest version of SSMA as soon as it is available.
  • SSMA installable binaries are now delivered through Windows installer package files (.msi).

Resources

Extending SQL Server Migration Assistant's conversion capabilities

Assess and migrate data from non Microsoft data platforms to SQL Server (with Oracle example)

May 2016

The May 2016 release of SSMA for Sybase contains the following changes:

  • Added support for SQL Server 2016.
  • Removed installer check for .Net 2.0.
  • Updated Extension Pack dependency from .Net 3.5 to .Net 4.0.
  • Fixed "save project" and "open project" commands for SSMA Console.
  • Fixed "securepassword" command for SSMA Console.
  • Fixed counting of objects for initial loading.
  • Fixed bug in global settings.

March 2016

The March 2016 preview release of SSMA for Sybase contains the following changes:

  • Added support for migration to SQL Server 2016.

January 2016

The January 2016 maintenance release of SSMA for Sybase contains the following changes:

  • Added View Log Menu Item to SSMA (RFC 5706203).
  • Added Telemetry.

July 2014

The July 2014 release of SSMA for Sybase contains the following changes:

  • Improved Azure SQL DB code conversion.
  • Moved extension pack functionality to schema to support Azure SQL DB.
  • Added performance improvements tested for databases with over 10k objects.
  • Added UI improvements for dealing with large number of objects.
  • Added the ability to highlight “well known” LOB schemas (so they can be ignored in conversion).
  • Added conversion speed improvements.
  • Added the ability to show object counts in UI.
  • Reduced report size by more than 25%.
  • Improved error messages for unparsed constructs.

April 2014

The April 2014 release of SSMA for Sybase contains the following changes:

  • Added support of MS SQL Server 2014.
  • Fixed bugs regarding conversion to Azure.
  • Fixed bugs regarding invisible report pages in IE 10.

January 2012

The January 2012 release of SSMA for Sybase contains the following changes:

  • Added support for rollback trigger conversion.
  • Provided fix for converting @@ROWCOUNT and @@ERROR in the same SET statement.

July 2011

The July 2011 release of SSMA for Sybase contains the following changes:

  • Improved error reporting during data migration.

April 2011

The April 2011 release of SSMA for Sybase contains the following changes:

  • Consolidated “SSMA for Sybase” product, which supports SQL Server 2005, SQL Server 2008, SQL Server “Denali” and Azure SQL.
  • Added support for connecting and migrating to SQL Server “Denali.”
  • Added a new feature to convert and migrate Sybase databases to Azure SQL.
  • Enhanced client-side data migration engine, supporting parallel migration of data.
  • Improved data migration performance with Simple and Bulk logged recovery models.
  • Added the ability to properly convert and migrate case-sensitive Sybase databases to case-sensitive SQL Server.
  • Added support for conversion of Sybase ASE Non-ANSI join statements to SQL Server ANSI join statements has been extended to DELETE and UPDATE statements.
  • Provided additional connectivity options for connecting to Sybase ASE servers using Sybase ASE ODBC provider and Sybase ASE ADO.Net providers.
  • Removed the dependency on a separate database called SysDB, which contains the Sybase emulation functions (installed as part of Extension Pack).
  • Added the ability to install SSMA for Sybase Extension Pack on SQL Server clusters.
  • Added backward compatibility of projects created by earlier versions of SSMA (v4.0 and v4.2).
  • Added the ability to install the SSMA for Sybase v5.0 product side-by-side (SxS) with older versions of SSMA (v4.0 and v4.2).

July 2010

The July 2010 release of SSMA for Sybase contains the following changes:

  • Added support for migrating to SQL Server 2008 R2.
  • Added a new SSMA Console application for command-line execution.
  • Added support for Data Migration using both Server-Side and Client-Side Data Migration Engines.
  • Added support for “Custom SELECT” statement in data migration.
  • Added support for migrating from Sybase ASE 15.0.3 and 15.5.

June 2008

The June 2008 release of SSMA for Sybase contains the following changes:

  • Added SSMA Tester, which automatically tests the database object conversion and the data migration made by SSMA. After all SSMA migration steps are finished, use SSMA Tester to verify that converted objects work the same way and that all data was transferred properly.
  • Added Pre-SQL conversion. User now can specify temporary table (and other object) declarations for each source procedure to be used in conversion.
  • Added improvements in object conversion:
    • Joins conversion revised.
    • Aggregates and non-aggregates without having/group by clauses.
    • The IDENTITY function with a SELECT INTO statement.
    • Clustered constraints and indexes on data-only-locked.
    • Temporary tables created by SELECT INTO.
    • Constraints / Indexes for temporary tables.
    • New SQL Server 2008 datetime types are supported.
    • Sybase 15.0 connectivity and datatypes support.

May 2007

The May 2007 release of SSMA for Sybase contains the following changes:

  • Added the ability to load database content faster when saving a project.
  • Added support for user-entered comments in the SQL Server formatted SQL mode.
  • Added improvements in object conversion.

The Help file was not updated for this release. For more information, see the Documentation Notes section later in this topic.

November 2006

The November 2006 release of SSMA for Sybase contains the following changes:

  • Added new global settings:
    • You can opt to show line numbers in editor windows.
    • You can configure SSMA to prompt to replace duplicate objects, or always or never replace duplicate objects during schema conversion.
  • Added a new conversion option that lets you configure how SSMA handles the following situations:
    • A CAST or CONVERT statement that contains a binary string.
    • Checks for null values in equality expressions.
    • Proxy tables.
    • User message error numbers for RAISERROR.
    • UPDATE statements that contain unresolved identifiers.
  • Added a new migration option that lets you specify how SSMA should handle dates that are outside the SQL Server date range.
  • Added a Formatted SQL setting on the SQL tab, which formats the code for improved readability.
  • Bug fixes that include the following:
    • SSMA now converts LOCK TABLE table IN { SHARED | EXCLUSIVE } MODE statements by adding a TABLOCK or TABLOCKX hint to the subsequent SELECT query on the table.
    • The necessary casts are now added when binary types are used in character expressions.
    • Memory and performance improvements.

July 2006

The July 2006 release of SSMA for Sybase was the initial release.

See Also

Getting Started with SSMA for Sybase (SybaseToSQL)