My shop has an ongoing project which requires the use of Unicode.
A table in particular will be used to store error messages, labels, etc, of our software; the text will be stored in a unicode field. As I try to gather information about unicode data types in DB/2, I'd like to know if there are caveats that I must be aware of before taking a decision. I have to choose between NVARCHAR and NCLOB: appart from the fact that NCLOB will allow me to store bigger strings than NVARCHAR, are there performance issues which should be taken into consideration?
Thanks in advance for your upcoming advices :)
Pinned topic Need advices: dealing with unicode?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-10T15:34:56Z at 2013-01-10T15:34:56Z by krmilligan
krmilligan 120000MDWP450 Posts
Re: Need advices: dealing with unicode?2013-01-10T15:34:56ZThis is the accepted answer. This is the accepted answer.LOB columns are a little more work to read. In addition, the non-SQL native record-level access interfaces cannot be used with tables containing LOB columns.