Unicode to non-Unicode migration
(Doc ID 485700.1)
Last updated on JANUARY 25, 2020
Applies to:Siebel System Software - Version 7.8.2 SIA  and later
z*OBSOLETE: Microsoft Windows Server 2003
Version: 7.8.2  SVE Transp
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-2887646701.
We have installed our development environment successfully.
At database initiation in connection to the installation, Unicode was selected.
This was done as it was assumed that Unicode was the most reliable and scalable option, albeit less space efficient.
It is highly unlikely that the application will be rolled out to non-Swedish customers.
The client has since undergone a sizing review in which we indicated our plans of running Unicode for the entire implementation.
At this stage only development is installed.
The sizing review result says that Unicode will require roughly twice as much disc space as a non-Unicode setup would.
1. Does Siebel have any recommendation on using Unicode or not?
1a. Is using Unicode or not merely a question of what language(s) the application will run in?
1b. If the answer to 1a is No, what other aspects are significant (e.g. ETL execution time)?
2. Is it possible to keep the current development setup and run non-Unicode in e.g. test and production?
2a. For eBusiness - with regards to repository export/import etc?
2b. For Analytics - with regards to web catalogs etc?
3. Do you have any suggestions on how we should get our development database to non-Unicode? If possible we would like to keep the user data, i.e. the data we have created in development. We did not start to configure yet.
Thank for your feedback!
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