|
|
You're in the
sql server dts
group:DTS vs Job Problem for 2 Digit Date format
sql server dts:
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 ?
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 [quoted text, click to view] >-----Original Message-----
>Check the Date tab in the Regional Options control panel. > >-- >Thanks >Phill Carter >#562421 > >"Norm" <nbrault@sympatico.ca> wrote in message >news:16ba301c417b4$2b9195d0$a401280a@phx.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 > > >.
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 Nor ----- Phill wrote: ---- When you execute the DTS package it is running locally, so it will use th settings on your workstation. When it runs as from a scheduled job, it wil use the settings on the server "Norm" <anonymous@discussions.microsoft.com> wrote in messag news:13e2401c417b8$6293ef20$a601280a@phx.gbl.. [quoted text, click to view] > 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@sympatico.ca> wrote in messag >>news:16ba301c417b4$2b9195d0$a401280a@phx.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 >>>>>>
When you execute a DTS package it comes to you. It doesn't matter where it
is stored. it will be executed on the caller's PC and will use the caller's resources ergo when you execute it manually it is on your PC not the server. The job will execute on the server itself. -- ---------------------------- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org [quoted text, click to view] "Norm" <anonymous@discussions.microsoft.com> wrote in message news:03879F33-CDAF-431E-BF0F-C0FECDF3DA55@microsoft.com... > 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@discussions.microsoft.com> wrote in message > news:13e2401c417b8$6293ef20$a601280a@phx.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@sympatico.ca> wrote in message > >>news:16ba301c417b4$2b9195d0$a401280a@phx.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 > >>>>>>. > >>
The DTS & The job is execute directly on the server ?
Norm ----- Allan Mitchell wrote: ----- When you execute a DTS package it comes to you. It doesn't matter where it is stored. it will be executed on the caller's PC and will use the caller's resources ergo when you execute it manually it is on your PC not the server. The job will execute on the server itself. -- ---------------------------- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org [quoted text, click to view] "Norm" <anonymous@discussions.microsoft.com> wrote in message
news:03879F33-CDAF-431E-BF0F-C0FECDF3DA55@microsoft.com... > 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@discussions.microsoft.com> wrote in message > news:13e2401c417b8$6293ef20$a601280a@phx.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@sympatico.ca> wrote in message >>>news:16ba301c417b4$2b9195d0$a401280a@phx.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 >>>>>>>.
Check the Date tab in the Regional Options control panel.
-- Thanks Phill Carter #562421 [quoted text, click to view] "Norm" <nbrault@sympatico.ca> wrote in message news:16ba301c417b4$2b9195d0$a401280a@phx.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
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. [quoted text, click to view] "Norm" <anonymous@discussions.microsoft.com> wrote in message news:13e2401c417b8$6293ef20$a601280a@phx.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@sympatico.ca> wrote in message > >news:16ba301c417b4$2b9195d0$a401280a@phx.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 > > > > > >. > >
Forgot to Mention that if i run the DTS from The Agent or at the command Prompt my date format is ok it will show 2049 .
It seem to be only went i run from the Job Management were the date show 1949 .??? Need help please? Thanks ----- norm wrote: ----- The DTS & The job is execute directly on the server ? Norm ----- Allan Mitchell wrote: ----- When you execute a DTS package it comes to you. It doesn't matter where it is stored. it will be executed on the caller's PC and will use the caller's resources ergo when you execute it manually it is on your PC not the server. The job will execute on the server itself. -- ---------------------------- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org [quoted text, click to view] "Norm" <anonymous@discussions.microsoft.com> wrote in message
news:03879F33-CDAF-431E-BF0F-C0FECDF3DA55@microsoft.com... > 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@discussions.microsoft.com> wrote in message > news:13e2401c417b8$6293ef20$a601280a@phx.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@sympatico.ca> wrote in message >>>news:16ba301c417b4$2b9195d0$a401280a@phx.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 >>>>>>>.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |