Overview | Environments | Databases | Tables | Constraints | Datatypes | Queries | Updates | Example
Omnidex supports most SQL Server datatypes; however, care must be taken when mapping the SQL Server datatypes to Omnidex. Omnidex accesses SQL Server using the SQL Server ODBC Connector, and so the datatype correlations will follow the ODBC standard.
Omnidex has very limited support for Unicode datatypes, also known as National Character datatypes. Omnidex can retrieve and return these datatypes, but cannot index beyond the standard ASCII character set. The SQL Server NATIONAL datatypes should be declared as STRING or CHARACTER datatypes within Omnidex.
Omnidex does not support the SQL Server binary large object datatypes or the image datatypes.
The following table correlates the SQL Server and Omnidex datatypes:
| SQL Server Datatype | Omnidex Datatype | Comments |
|---|---|---|
| CHAR | CHAR(ACTER) | |
| VARCHAR | STRING or VARCHAR | Favor STRING unless your character data cannot be terminated by a NULL character. |
| NCHAR | NATIONAL CHAR(ACTER) | Omnidex has limited support for Unicode datatypes, but recommends the use of CHARACTER datatype. |
| NVARCHAR | NATIONAL VARCHAR | Omnidex has limited support for Unicode datatypes, but recommends the use of STRING datatype. |
| BIT | TINYINT | |
| TINYINT | TINYINT | |
| SMALLINT | SMALLINT | |
| INT | INTEGER | |
| BIGINT | BIGINT | |
| SMALLMONEY | DOUBLE | |
| MONEY | DOUBLE | |
| FLOAT | FLOAT | |
| REAL | DOUBLE | |
| DECIMAL | DOUBLE, CHAR(ACTER) | |
| DATE | ODBC DATE | |
| SMALLDATETIME | ODBC DATETIME | |
| DATETIME | ODBC DATETIME | |
| DATETIMEOFFSET | ODBC DATETIME | |
| DATETIME2 | ODBC DATETIME | |
| TEXT | STRING or CLOB | Favor STRING unless your character data cannot be terminated by a NULL character. |
| BINARY | Unsupported | |
| VARBINARY | Unsupported | |
| IMAGE | Unsupported |
See also: