Page 2 of 2

Posted: Mon Aug 25, 2008 12:42 pm
by chulett
I'm lost on how using a varchar doesn't get you the "real time" it takes to load the data.

And you don't change the NLS_DATE format, you match it and use a varchar. That's the only mechanism for loading a date that does not require the use of the TO_DATE function.

Posted: Mon Aug 25, 2008 2:52 pm
by bolingo
The issue is solve by using User insert command like:
INSERT
INTO
TBble
(T_ID, T_DATE)
VALUES
(ORCHESTRATE.T_ID, to_date(ORCHESTRATE.T_DATE, 'yyyy/mm/dd'))


In the ODBC enterprise stage, I declare t_date varchar;

in open command property I use this query : TRUNCATE TABLE TBble;

Thanks all of you for helping me;

Posted: Mon Aug 25, 2008 2:54 pm
by bolingo
The issue is solve by using User insert command like:
INSERT
INTO
TBble
(T_ID, T_DATE)
VALUES
(ORCHESTRATE.T_ID, to_date(ORCHESTRATE.T_DATE, 'yyyy/mm/dd'))


In the ODBC enterprise stage, I declare t_date varchar;

in open command property I use this query : TRUNCATE TABLE TBble;

Thanks all of you for helping me;

Posted: Mon Aug 25, 2008 2:56 pm
by chulett
Interesting... you've said all along the date was in YYYY-MM-DD format and yet a mask of YYYY/MM/DD works for you? Ok.

Anyway, glad it is sorted out regardless.