How can we help?
Search for answers or browse our knowledge base
Recommended field types
For each of the connection types used for the GTServer client database, here are the recommended field types for the tables specified in the launch actions and the integration actions:
| Field type | SQL Server 2005 | SQL Server 2008 to 2014 | Oracle | Postgres | DB2 |
|---|---|---|---|---|---|
| Integer | int | int | number(10) | int | integer |
| Real | float | float | binary_double | double precision | double |
| Limited text (p char.) | nvarchar(p) | nvarchar(p) | varchar2(p) | varchar(p) | varchar(p) |
| Long text | nvarchar(max) | nvarchar(max) | clob | text | clob |
| Date and time | datetime | datetime | timestamp | timestamp without time zone | timestamp |
| Date | datetime | date | date | date | date |
| Time | datetime | time | timestamp | time without time zone | time |
| Check box | tinyint | tinyint | number(3) | smallint | tinyint ou int |
In the case of SQL Server, the recommended field types depend on the DBMS version AND the type of connection chosen in GTServer.
Boolean or bit fields should generally be avoided as the data storage or driver behaviour is often unsatisfactory.
Non-variable length text fields (char or nchar for most databases) are strongly discouraged (spaces may be added when GTServer extracts the data)