NLS LANG / Charactersets in SQL Server Database Compatibilty

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Aquilis
Participant
Posts: 204
Joined: Thu Apr 05, 2007 4:54 am
Location: Bangalore
Contact:

NLS LANG / Charactersets in SQL Server Database Compatibilty

Post by Aquilis »

Hi,
I use SQL Server as source and Oracle as Destination database. Am following SCD-Type 1 approach. When SCD Stage is in place, it always sends data as changed data even though there are no Changes literally happened at source.

SQL Server database has :
COLLATION_NAME as - "SQL_Latin1_General_CP1_CI_AS".

Oracle Destination Database has-
NLS_NCHAR_CHARACTERSET: AL16UTF16
NLS_LANGUAGE: AMERICAN
NLS_TERRITORY: AMERICA

I have updated the 'odbc.ini' file to - IANAAppCodePage=2252 and tried most of the combination of Charactersets and NLS_LANG (user_defined: environmental variable).
Any suggestions, how SCD Stage behaves in this situations ?
Aquilis
Aquilis
Participant
Posts: 204
Joined: Thu Apr 05, 2007 4:54 am
Location: Bangalore
Contact:

Post by Aquilis »

SQL Server database records had multiple Control Characters.

There are various control Characters involved and SCD Stage (type-1) needs data to be control Characters free.

So I have shifted to use CDC (Change Data Capture) along with IANAAppCodePage=2252 in 'odbc.ini' file and issue has sorted out.

No longer am using SCD Stage to avoid data cleansing as there is different layer for cleansing in our application.

Many thanks,
Aquilis
Post Reply