Database field data types

The following table lists the database field data types supported by Content Manager OnDemand.

Field Type	Description	Field Size (Db2)	Field Size (Oracle)	Field Size (SQL Server)
Small Int	Contains whole numbers between -32768 and 32,767.	2 bytes	21 bytes	2 bytes
Integer	Contains whole numbers between -2147483648 and 2147483647.	4 bytes	21 bytes	4 bytes
Big Int	Contains whole numbers between -9223372036854775808 and 9223372036854775807.	8 bytes	21 bytes	8 bytes
Decimal	Contains numbers between 10(307) and 10(308) with up to 15 significant digits.	8 bytes	21 bytes	8 bytes
DecFloat (16)	Decimal floating-point number with 16 digits of precision.	8 bytes	Not available	Not available
DecFloat (34)	Decimal floating-point number with 34 digits of precision.	16 bytes	Not available	Not available
String (Fixed)	Contains letters, numbers, special symbols, such as the % and #, and any other printable character.	1 - 254 bytes. For SBCS string: 1 byte per character For MBCS string: Up to 4 bytes per character	1 - 254 bytes. For SBCS string: 1 byte per character For MBCS string: Up to 4 bytes per character	1 - 254 bytes. For SBCS string: 1 byte per character For MBCS string: Up to 4 bytes per character
String (Variable)	Contains letters, numbers, special symbols, such as the % and #, and any other printable character.	1 - 2000 bytes. For SBCS string: 1 byte per character plus 2 bytes of overhead For MBCS string: Up to 4 bytes per character plus 2 bytes of overhead Unused bytes do not use storage. See your database documentation for more information on variable string type.	1 - 2000 bytes. For SBCS string: 1 byte per character plus 2 bytes of overhead For MBCS string: Up to 4 bytes per character plus 2 bytes of overhead Unused bytes do not use storage. See your database documentation for more information on variable string type.	1 - 2000 bytes. For SBCS string: 1 byte per character plus 2 bytes of overhead For MBCS string: Up to 4 bytes per character plus 2 bytes of overhead Unused bytes do not use storage. See your database documentation for more information on variable string type.
Date	Contains a valid date from January 1, 0001 to December 31, 9999.	4 bytes	7 bytes	3 bytes
Date (old style)	Contains a valid date from January 1, 1970 to December 31, 2058.	2 bytes	2 bytes	2 bytes
Time (old style)	Contains times of day, stored in three second increments, since midnight, and limited to 24 hours.	2 bytes	2 bytes	2 bytes
Date/Time	Contains a valid date from January 1, 0001 to December 31, 9999.	13 bytes	11 bytes	8 bytes
Date/Time (old style)	Contains both a date and time value. The date can be from January 1, 1970 to January 18, 2038. The time is stored in one second increments.	4 bytes	4 bytes	4 bytes
Date/Time (TZ)	Contains a valid date from January 1, 0001 to December 31, 9999.	13 bytes	11 bytes	8 bytes
Date/Time (TZ) (old style)	Contains both a date and time value. A Date/Time (TZ) field is exactly like a Date/Time field, but uses the time zone from the client.	4 bytes	4 bytes	4 bytes

The Date, Date/Time, and Date/Time (TZ) field types introduced in Content Manager OnDemand Version 9.0 are not compatible with clients from previous releases. If you must retain compatibility with clients from previous releases, use the Date (old style), Date/Time (old style), and Date/Time (TZ) (old style) field types.

A Time (old style) field cannot be added to a new or existing application group. An application group with a Time (old style) field can be copied on the same server or exported to a different server.

When storing indexes in a UTF-8 instance, it is important to note that some characters will use more than one byte when stored in a UTF-8 field. Latin lowercase and uppercase characters [a-z] [A-Z] and Arabic numerals [0-9] use only one byte. Accented characters might use two bytes. MBCS characters might use two, three, or four bytes.