We are trying to come up with different approaches.
1) 2 App. instances, one for US and the other for China, with 2 different databases, one for US and the other for China
2) 2 App. instances, one for US and the other for China, with 1 centralized database both for US and China
3) Single application instance with 2 different databases, one for US and the other for China
4) Single application instances with 1 centralized database both for US and China
Some consideration :
1. would there be any data sharing between the two databases?
2. would US app access China app, or vice versa? real-time or data delay is permitted?
if yes to 1 and 2 (real-time), then I think having a single database would benefit you; but if 2(with delay), I think either standalone database for either side with sychronisation (AQ) or batch file
Also same as mrjoltcola, you may need to configure the database using UTF8 or UTF16 is ok for your needs.
Main Topics
Browse All Topics
by: mrjoltcolaPosted on 2009-10-12 at 07:52:16ID: 25551732
Yes, you can use a shared database IF you choose a UNICODE capable character set, like UTF8 or UTF16.
Depending on which language will be stored the most one will be more space efficient than the other
If most of the data will be US/ASCII, you may choose UTF8 (Oracle char set AL32UTF8). ASCII only requires 1 byte per character, and in UTF8, ASCII is not encoded so there is no conversion.
If most of the data will be Chinese / Asian, AL32UTF16 will be more space efficient. Chinese will require 2 bytes per character.
http://download.oracle.com
Oracle docs suggest AL32UTF16 for Asian databases. But either UTF setting will encode all languages.