Global Deployment Guide > Global Deployment Scenarios > Global Deployment Scenarios >

Non-Unicode Database Deployment


If you do not have multiple users in different locales that require access to the same data, you can use a non-Unicode database in your deployment. This would be similar to the monolingual data support scenario, as shown in Figure 3.

This type of deployment is simpler to set up, configure, and deploy. However, the disadvantage to this scenario is that data can only be represented in a limited set of languages.

The decision on whether to use a Unicode or non-Unicode database should be based on whether all required languages can be represented by one code page. For Siebel eBusiness Applications version 7.5 non-Unicode database deployments, you must choose a database encoding of:

NOTE:  Any broader set of required characters requires using a Unicode database.


 Global Deployment Guide 
 Published: 18 April 2003