Choosing a database character set means choosing Unicode
(Doc ID 333489.1)
Last updated on NOVEMBER 08, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 8.0.3.0 to 12.1.0.1 [Release 8.0.3 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 21-Jul-2017***
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 8.0.3.0 to 12.1.0.1.0
Purpose
Designing and setting up a new database system can take a lot of planning. But typically, one important decision is overlooked: choosing the right character set.
A basic consideration for choosing a character set is to make sure it can handle any language that needs to be supported immediately and in the indeterminate future. Another overlooked consideration is to think about what applications and technologies you may want to utilize or interact with the database. Choosing Unicode as the database character set ensures a strong foundation for whatever is built into and on top of the database.
Scope
This note is a summary of an article which used to be available on the Oracle Technology Network called "The Unicode Imperative - Deploying a new database system starts with Unicode". The full article is no longer available, but this note will remain available to highlight the main arguments and conclusion.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| References |