Re: Remedy 7.5 and utf8

It looks like the number of bytes per character varies between db implementations as well. Oracle's AL32UTF8 uses 3 bytes per character. Your SQL Server looks like it uses 2 bytes per character for whatever character set you are using. On Oracle, Remedy defines the column size according to the w

Re: Remedy 7.5 and utf8

Hi, WARNING!!! I got a friendly note from BMC about this, and they reserve extra space in the database to fit any potential data into the fields. This means that it is not as easy as changing the attribute, as the storage of the field in the database can change to CLOB etc, depending on database

Re: Remedy 7.5 and utf8

Hi, To do an automatic change to CHAR instead of BYTES, I see three ways to do this. 1. Create an API-program that updated all character fields Downsides: There may be a ARAPI-version problem that corrupts the CharLimitsStruct if the API-program is of a different version 2. Export a def-file, ma

Re: Remedy 7.5 and utf8

Hi, I just saw something... You can change the "Length Unit" in the database properties of your field. The possible values are "Bytes" and "Characters". The default is "Bytes", but if you change this setting for all of your character fields, the old field length should be able to hold all your

Re: Remedy 7.5 and utf8

Hi, I have not tried this on Informix, but on Sybase, Oracle and MS-SQL. Remedy counts bytes, so the 255-byte character field will still be 255 bytes long. The problem is when you migrate your data, where a 255-character string will not allways fit in 255-bytes. In 99% of the cases, the string w

Remedy 7.5 and utf8

Hi, I've got the question about Remedy (7.5) and Informix (utf8). We are going to migrate the workflow and data from Remedy 7.1 (Informix cp-1257) to Remedy 7.5 (Informix utf8). As far as I know the ARS 7.5 allows to set the Length Unit to Characters (not Bytes). What will happen with data if the