Date handling weirdness in SQLServer hsodbc

Question

Folks, I am getting some weird stuff happening while using hsodbc for sqlserver, pulling from a view, with sqlserver columns of type datetime.
Using sqlserver tools I can see that the source data in some instances is for year 1900 (default) and in other cases year 2100 (our future enddate). In both of these cases though a very simple mapping to store the data in Oracle results in getting the year 2000 for both of them. What are my options? What is the reason for this condition?
Thanks in advance.
Regards,
ak

Answer 1

Could be related to the NLS_DATE_FORMAT setting.
Just inserted dates with year 1900 and 2100 into a SQL Server demo table.
At the ODBC driver manager make sure MS SQL Server ODBC driver does NOT have the use regional setting for outputting currency, numbers, dates and times checked.
SQL> alter session set nls_date_format='dd.mm.yyyy';
SQL> select * from "datetest"@sqlserver where "col1" < to_date('10.02.2005','dd.mm.yyyy');
col1
30.01.1900
10.01.1900
10.12.1900
SQL> select * from "datetest"@sqlserver where "col1" > to_date('10.02.2008','dd.mm.yyyy');
col1
10.02.2100
10.01.2100
30.01.2100
BUT:
SQL> alter session set nls_date_format='dd-mon-rr';
Session altered.
SQL> select * from "datetest"@sqlserver where "col1" > to_date('10.02.2008','dd.mm.yyyy');
col1
10-feb-00
10-jan-00
30-jan-00
SQL> select * from "datetest"@sqlserver where "col1" < to_date('10.02.2005','dd.mm.yyyy');
col1
30-jan-00
10-jan-00
10-dec-00
So please make sure the NLS_DATE_FORMAT is properly set AND the option in the ODBC driver is unchecked.
A couple of issues are also mentioned in:
Article-ID: Note 69029.1
Title: Implicit DATE Conversions - Issues to be aware of