You are not able to migrate your Oracle or Sybase databases to a case-sensitive SQL Server database using SSMA


Symptoms


When you try to migrate your Oracle or a Sybase database to a case-sensitive database on SQL Server using either SQL Server Migration Assistant for Oracle or SQL Server Migration Assistant for Sybase you may run into various error messages.

Cause


SSMA does not fully support the migration of source databases to a case-sensitive database on SQL Server.1

Resolution


Failures originating from case-sensitivity issues need to addressed manually. For example, if the schema contains two names with the same name but only differs in casing, SSMA results in errors that can be addressed manually by making the object names unique. Though full support of case-sensitive database does not exist in SSMA, users can still benefit from using the tool when there are no conflicts.