Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6356345
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T22:56:38+00:00 2026-05-24T22:56:38+00:00

I am in the process of upgrading an Oracle DB to SQL Server. Currently

  • 0

I am in the process of upgrading an Oracle DB to SQL Server. Currently the Oracle DB’s collation is set to WE8ISO8859P1 (binary case sensitive Eastern European character set that allows for double byte characters). Can anyone point me to what SQL Server collation will be closest to this?

Thanks!

Clay

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T22:56:39+00:00Added an answer on May 24, 2026 at 10:56 pm

    Your best option normally would be to use the SQL Server default collation (SQL_Latin1_General_CP1_CI_AS). If you have data that is constrained as unique but would be duplicated (cause violations) when case insensitive (SQL Default where Oracle is case sensitive) then you will either need to update your data to be case insensitive or choose a case sensitive collation.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We're in the process of upgrading one of our SQL Server instances from 2000
We are in the process of upgrading our sql server to 2K8 R2 and
I'm currently in the process of upgrading the TFS server from 2008 to 2010
I'm currently in the process of upgrading old II6 automation scripts that use the
We are currently in the process of upgrading our rails version and I have
We have in the process of upgrading our application to full Unicode comptibility as
We are in the process of upgrading our VS2008 to the new SP1, but
We are in the process of upgrading our projects from C# 2.0 / VS2005
We are in the process of upgrading to WebSphere 7.0 on Windows 2008 R2.
I am in a process of upgrading a c# MVC2 project into c# MVC4.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.