 | |
DTS vs Job Problem for 2 Digit Date format
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
DTS vs Job Problem for 2 Digit Date format -
04-01-2004
, 01:40 AM
#2
| |||
| |||
|
|
I've create a DTS package to load a text Document to a existing table into SQL ,one of the field is a datetime field,went i execute the package manually i get a date of 2049 for a 2 digit year of 01/01/49 but went i execute the same DTS thru a Job i get a date of 01/01/1949 . Does anyone experience the same problem? Any idea how this can be fix ? Thanks |
#3
| |||
| |||
|
|
-----Original Message----- Check the Date tab in the Regional Options control panel. -- Thanks Phill Carter #562421 "Norm" <nbrault (AT) sympatico (DOT) ca> wrote in message news:16ba301c417b4$2b9195d0$a401280a (AT) phx (DOT) gbl... I've create a DTS package to load a text Document to a existing table into SQL ,one of the field is a datetime field,went i execute the package manually i get a date of 2049 for a 2 digit year of 01/01/49 but went i execute the same DTS thru a Job i get a date of 01/01/1949 . Does anyone experience the same problem? Any idea how this can be fix ? Thanks . |
#4
| |||
| |||
|
|
I did that , Like i mention it is working ok if i execute the package by itself into the dts but as soon as i schedule a Job the date get's import as 1949 instead of 2049 I also change the SQL option to start date of 1967 -----Original Message----- Check the Date tab in the Regional Options control panel. -- Thanks Phill Carter #562421 "Norm" <nbrault (AT) sympatico (DOT) ca> wrote in message news:16ba301c417b4$2b9195d0$a401280a (AT) phx (DOT) gbl... I've create a DTS package to load a text Document to a existing table into SQL ,one of the field is a datetime field,went i execute the package manually i get a date of 2049 for a 2 digit year of 01/01/49 but went i execute the same DTS thru a Job i get a date of 01/01/1949 . Does anyone experience the same problem? Any idea how this can be fix ? Thanks . |
#5
| |||
| |||
|
|
I did that , Like i mention it is working ok if i execut the package by itself into the dts but as soon as schedule a Job the date get's import as 1949 instead o 204 I also change the SQL option to start date of 196 -----Original Message---- Check the Date tab in the Regional Options control panel -- Thank Phill Carte #56242 "Norm" <nbrault (AT) sympatico (DOT) ca> wrote in messag news:16ba301c417b4$2b9195d0$a401280a (AT) phx (DOT) gbl.. I've create a DTS package to load a text Document to existing table into SQL ,one of the field is a datetim field,went i execute the package manually i get a dat o 2049 for a 2 digit year of 01/01/49 but went i execut th same DTS thru a Job i get a date of 01/01/1949 Does anyone experience the same problem Any idea how this can be fix Thank |
#6
| |||
| |||
|
|
But the Jobs is execute on the same server itself where the DTS package is store. The Job was created from the DTS to run on that server? Norm ----- Phill wrote: ----- When you execute the DTS package it is running locally, so it will use the settings on your workstation. When it runs as from a scheduled job, it will use the settings on the server. "Norm" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:13e2401c417b8$6293ef20$a601280a (AT) phx (DOT) gbl... I did that , Like i mention it is working ok if i execute the package by itself into the dts but as soon as i schedule a Job the date get's import as 1949 instead of 2049 I also change the SQL option to start date of 1967 -----Original Message----- Check the Date tab in the Regional Options control panel. -- Thanks Phill Carter #562421 "Norm" <nbrault (AT) sympatico (DOT) ca> wrote in message news:16ba301c417b4$2b9195d0$a401280a (AT) phx (DOT) gbl... I've create a DTS package to load a text Document to a existing table into SQL ,one of the field is a datetime field,went i execute the package manually i get a date of 2049 for a 2 digit year of 01/01/49 but went i execute the same DTS thru a Job i get a date of 01/01/1949 . Does anyone experience the same problem? Any idea how this can be fix ? Thanks . |
#7
| |||
| |||
|
|
But the Jobs is execute on the same server itself where the DTS package is store. The Job was created from the DTS to run on that server? Norm ----- Phill wrote: ----- When you execute the DTS package it is running locally, so it will use the settings on your workstation. When it runs as from a scheduled job, it will use the settings on the server. "Norm" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:13e2401c417b8$6293ef20$a601280a (AT) phx (DOT) gbl... I did that , Like i mention it is working ok if i execute the package by itself into the dts but as soon as i schedule a Job the date get's import as 1949 instead of 2049 I also change the SQL option to start date of 1967 -----Original Message----- Check the Date tab in the Regional Options control panel. -- Thanks Phill Carter #562421 "Norm" <nbrault (AT) sympatico (DOT) ca> wrote in message news:16ba301c417b4$2b9195d0$a401280a (AT) phx (DOT) gbl... I've create a DTS package to load a text Document to a existing table into SQL ,one of the field is a datetime field,went i execute the package manually i get a date of 2049 for a 2 digit year of 01/01/49 but went i execute the same DTS thru a Job i get a date of 01/01/1949 . Does anyone experience the same problem? Any idea how this can be fix ? Thanks . |
#8
| |||
| |||
|
|
But the Jobs is execute on the same server itself where the DTS package is store. The Job was created from the DTS to run on that server? Norm ----- Phill wrote: ----- When you execute the DTS package it is running locally, so it will use the settings on your workstation. When it runs as from a scheduled job, it will use the settings on the server. "Norm" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:13e2401c417b8$6293ef20$a601280a (AT) phx (DOT) gbl... I did that , Like i mention it is working ok if i execute the package by itself into the dts but as soon as i schedule a Job the date get's import as 1949 instead of 2049 I also change the SQL option to start date of 1967 -----Original Message----- Check the Date tab in the Regional Options control panel. -- Thanks Phill Carter #562421 "Norm" <nbrault (AT) sympatico (DOT) ca> wrote in message news:16ba301c417b4$2b9195d0$a401280a (AT) phx (DOT) gbl... I've create a DTS package to load a text Document to a existing table into SQL ,one of the field is a datetime field,went i execute the package manually i get a date of 2049 for a 2 digit year of 01/01/49 but went i execute the same DTS thru a Job i get a date of 01/01/1949 . Does anyone experience the same problem? Any idea how this can be fix ? Thanks . |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.