SSMA Blog

SSMA for MySQL

srirambalaji — Fri, 08 Jan 2010 07:25:07 +0000

SQL Server Migration Assistant for MySQL is newest addition to the SSMA family!

Microsoft SQL Server Migration Assistant (SSMA) 2008 is a toolkit that dramatically cuts the effort, cost, and risk of migrating from MySQL to SQL Server 2008 and SQL Azure. SSMA 2008 for MySQL v1.0 CTP1 provides an assessment of migration efforts as well as automates schema and data migration. It is first member of SSMA product family which includes support for SQL Azure.

SSMA 2008 for MySQL v1.0 CTP1 is designed to work with MySQL 4.1, 5.0 and 5.1 and all editions of SQL Server 2008 or SQL Azure.
You can download the tool from the links below.

SSMA 2008 for MySQL v1.0 CTP1

SSMA 2005 for MySQL v1.0 CTP1

SQL Server 2008 Migration Whitepapers

srirambalaji — Wed, 09 Sep 2009 04:02:44 +0000

Microsoft has recently released whitepapers which help to migrate from other databases to SQL Server 2008.

Guide to Migrating from Oracle to SQL Server 2008
This white paper explores challenges that arise when you migrate from an Oracle 7.3 database or later to SQL Server 2008. It describes the implementation differences of database objects, SQL dialects, and procedural code between the two platforms. The entire migration process using SQL Server Migration Assistant (SSMA) 2008 for Oracle is explained in depth, with a special focus on converting database objects and PL/SQL code.

Guide to Migrating from Sybase ASA to SQL Server 2008
This white paper explores challenges that arise when you migrate from a Sybase Adaptive Server Anywhere (ASA) database of version 9 or later to SQL Server 2008. It describes the implementation differences of database objects, SQL dialects, and procedural code between the two platforms.

Guide to Migrating from Sybase ASE to SQL Server 2008
This white paper covers known issues for migrating Sybase Adaptive Server Enterprise database to SQL Server 2008. Instructions for handling the differences between the two platforms are included. The paper describes how SQL Server Migration Assistant, the best tool for this type of migration, can help resolve various migration issues.

Guide to Migrating from MySQL to SQL Server 2008
In this migration guide you will learn the differences between the MySQL and SQL Server 2008 database platforms, and the steps necessary to convert a MySQL database to SQL Server.

Guide to Migrating from Informix to SQL Server 2008
This white paper explores challenges that arise when you migrate from an Informix 11 database to SQL Server 2008. It describes the implementation differences of database objects and procedural code between the two platforms. Emulation of system functions is also discussed.

You can download these whitepapers from here.

SSMA Links Listing

srirambalaji — Tue, 08 Sep 2009 11:37:00 +0000

In this section I will list down all the interesting and useful links on the internet on SSMA and SQL Server migration. I will try to update this frequently with new links.

SQL Server 2008 Migration Assistants Downloads
SSMA 2008 for Oracle
SSMA 2008 for Oracle automates the end to end database migration process from Oracle to SQL Server 2008. It performs assessment, schema migration, data migration and validation of migrated database objects.

SSMA 2008 for Sybase ASE
SSMA 2008 for Oracle automates the database migration process from Sybase ASE to SQL Server 2008. It performs assessment, schema migration, data migration and validation of migrated database objects.

SSMA 2008 for Access
SSMA 2008 for Oracle automates the database migration process from Access to SQL Server 2008. It converts Access database objects to SQL Server database objects and performs the data migration. It supports Access 97 – Access 2007 databases.

SSMA 2008 for Sybase PowerBuilder Applications
SSMA 2008 for Sybase PowerBuilder Applications is a tool that cuts the effort, cost, and risk of migrating PowerBuilder Applications designed for Sybase ASE to SQL Server 2008.

SQL Server 2005 Migration Assistants Downloads
SSMA 2005 for Oracle
SSMA 2005 for Oracle automates the database migration process from Oracle to SQL Server 2005.

SSMA 2005 for Sybase ASE
SSMA 2005 for Sybase ASE automates the database migration process from Sybase ASE to SQL Server 2005.

SSMA 2005 for Access
SSMA 2005 for Access automates the database migration process from Access to SQL Server 2005.

SQL Server Migration Solutions Center

SSMA Forums
microsoft.public.sqlserver.migrationassistant

Migration Whitepapers

Migrating to SQL Server 2008

Guide to Migrating from Oracle to SQL Server 2008

Guide to Migrating from Sybase ASA to SQL Server 2008

Guide to Migrating from Sybase ASE to SQL Server 2008

Guide to Migrating from MySQL to SQL Server 2008

Guide to Migrating from Informix to SQL Server 2008

Migrating to SQL Server 2005

Guide to Migrating from Oracle to SQL Server 2005 using SSMA

Guide to Migrating from Sybase ASE to SQL Server 2005 using SSMA

Migrating from MySQL to SQL Server 2005

DB2 to SQL Server Migration Guide

Guide to Migrating from Microsoft Access to SQL Server 2005

Optimizing Microsoft Office Access Applications Linked to SQL Server

Solution Guides
Solution for Migrating from Oracle on UNIX to SQL Server on Windows

Solution Guide for Sybase/UNIX to SQL Server

SSMA Knowledgebase

SSMA Error Messages and Warning Messages Reference

How to Articles
Migration to SQL Server Express using SSMA Oracle PDF

SSMA Warning O2SS0259: CURSOR type was converted to varchar(8000).

srirambalaji — Mon, 10 Aug 2009 11:00:00 +0000

Explanation
SQL Server returns cursors in different way than Oracle. SSMA converts cursor parameter to a VARCHAR parameter to keep procedure parameter count, but converts OPEN FOR statement inside stored procedure into a SELECT statement. This works in most cases when procedure is called from outside (client application).
In general, you can safely ignore this warning, because all places which require attention because of this migration issue (passing a cursor as a parameter) are marked with other errors with proper “migration hours” assigned.

More Information
Warning

Applies to
• SSMA 2005 for Oracle
• SSMA 2008 for Oracle

SSMA Error S2SS0002: The following SQL statement cannot be converted:

srirambalaji — Mon, 10 Aug 2009 06:51:41 +0000

Explanation
S2SS0002: The following SQL statement cannot be converted:
/*
* ROLLBACK TRIGGER WITH
* RAISERROR 130506 @var
*/
Suggest you to convert these statements manually. Actually, rollback trigger statements are supported in sybase but not supported in sql server so it requires some changes.

You can refer to this article:
http://www.devarticles.com/c/a/SQL-Server/Migrating-from-Sybase-to-SQL-Server/1/

More Information
Error

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

S2SS0002: The following SQL statement cannot be converted:

srirambalaji — Tue, 04 Aug 2009 16:03:00 +0000

You can refer to this article:
http://www.devarticles.com/c/a/SQL-Server/Migrating-from-Sybase-to-SQL-Server/1/

More Information
Error

Applies to
• SSMA 2005 for Sybase
• SSMA 2008 for Sybase

Not able to convert Parameterized Queries

srirambalaji — Tue, 04 Aug 2009 07:27:00 +0000

Symptom
SSMA Access is not able to convert parameterized queries.
Eg: “>=[forms]![Date_Range]![BeginDate]
Cause
The current version of SSMA doesn’t support parameterized queries.

Resolution
The current version of SSMA doesn’t support parameterized queries. Need to manually convert the queries.

Applies to
• SSMA 2008 for Access

Nothing to Process error when creating Assessment report

srirambalaji — Tue, 04 Aug 2009 07:17:00 +0000

Symptom
When user tries to create Assessment Report by click “Create Report” they may get error “There is Nothing to process”

Cause
We get this message if there are no objects in the node selected.

Resolution

As there are no objects in any of the schemas(as shown above) you are getting that message ”There is nothing to process”. You can create report only when you have objects(tables,Procedures etc) in the node selected.
In the above the user guest does not have access to any database objects. So there are no objects under guest schema. If the above user is given permission to those objects, then those objects will be visible in Metadeta explorer. Then you won’t get this error message.

UDF not converted by SSMA

srirambalaji — Tue, 04 Aug 2009 07:16:00 +0000

Symptom
When using ASE 15.0.2 version SSMA is not able to convert the User Defined functions.

Cause
SSMA does not support this Sybase version

Resolution
User defined functions have to be converted manually.
UDF were introduced in Sybase ASE 15.0.2and SSMA for Sybase v4.0 doesn’t support this version.

Text columns get truncated to a size of 32K

srirambalaji — Tue, 04 Aug 2009 07:14:00 +0000

Symptom
When using SSMA 2008 for Sybase for Data migration “text” columns may get truncated to a maximum of 32K

Cause
Text columns can get truncated because of default value of textsize property.

Resolution
Text columns can get truncated because of default value of textsize property. The default size of TextSize attribute of Oledb provider is 32K so if the data is more than 32K , its getting truncated in your case.
As a workaround, you can set the connection string in advanced mode to connect to Sybase.

In the connection string include a parameter ‘textsize’ as shown and assign it the maximum number of characters you have in all your text columns ,so that it won’t truncate data.
Sample connection string:
User ID=myID;PWD=abc;Provider=ASEOLEDB.1;Server=myserver;Port=5000;Database=master;
textsize=;
(Note: Change Provider according to your version)