Easysoft ODBC-SQL Server Driver

Why does DG4ODBC report the wrong length for my SQL Server character columns?

Last Reviewed:
26th January 2024

If your Oracle database character set is UTF-8 (UTF8 or AL32UTF8), some versions of DG4ODBC will triple the length when describing character columns and pad character values with blanks. DG4ODBC does this because the UTF-8 character set may require up to three bytes to encode a character. The column length that DG4ODBC reports is based on the maximum number of bytes that may be required to store a column value rather than the maximum number of characters a column value may contain.

To illustrate this issue, we created the following table in SQL Server:

create table test_table (id_col int identity, char_col char(20))
insert into test_table values ('ABC')

Although the specified length for char_col was 20, the length that DG4ODBC reports for the column is three times this value:

SQL> select length ("char_col") from dbo.test_table@dg4odbc_link;


(The SQL Server ODBC driver reports the correct column length, as the following unixODBC driver manager log extract demonstrates.)

Column Name = [char_col]
Data Type = 0x7fff56ceaf48 -> 1
Column Size = 0x7fff56ceaee0 -> 20

Running the following query returns a blank-padded value: ABC, which is the value stored in the column, plus 57 blank characters, a total of 60 characters.

SQL> select "char_col" from dbo.test_table@dg4odbc_link;


You can change this behaviour by configuring DG4ODBC to be character orientated rather than byte orientated when reporting character column lengths. To do this:

  1. Add these lines to your initsid.ora file:
  2. Stop and start the Oracle Listener.
See Also
Applies To

Knowledge Base Feedback

* Did this content help you?
* Please select one option based on your first choice:

(* Required Fields)