Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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

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.

↑ Back to the top

Cause

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

↑ Back to the top

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.

↑ Back to the top

Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2020715
Revision : 1
Created on : 1/8/2017
Published on : 10/4/2010
Exists online : False
Views : 97