Is Unicode an overkill?
Posted: Fri Mar 11, 2016 11:44 pm
Hi DS Gurus,
I'm reviewing some of the code built by my peers and came across a scenario where we are not (and never will) dealing with UNICODE data. But all the metadata(output definitions) within DataStage have been defined as UNICODE. The jobs are fairly complex with lookups, joins, change captures, etc.
How much of an impact is this going to have in terms of performance or otherwise?
Would also appreciate if someone can point me to an exhaustive DS checklist.
Thank you
I'm reviewing some of the code built by my peers and came across a scenario where we are not (and never will) dealing with UNICODE data. But all the metadata(output definitions) within DataStage have been defined as UNICODE. The jobs are fairly complex with lookups, joins, change captures, etc.
How much of an impact is this going to have in terms of performance or otherwise?
Would also appreciate if someone can point me to an exhaustive DS checklist.
Thank you