Re: Incorrect DTS package version run by scheduled job

From: Sue Hoegemeier (Sue_H_at_nomail.please)
Date: 09/07/04 

Date: Tue, 07 Sep 2004 10:53:50 -0600

Thanks for posting back Craig. I never use the functionality of right
clicking on a package and use the Schedule Package. The encrypted
command line can make it difficult to troubleshoot job issues or to
move the jobs to other servers. I generally set packages up as jobs by
manually creating the job and the dtsrun command and using windows
authentication for the login. There isn't much that needs to be
encrypted then - unless you don't want job owners or sysadmins to know
what package is running in which job.

-Sue

On Tue, 7 Sep 2004 07:15:03 -0700, "Craig"
<CraigNicholas@online.nospam> wrote:

>I've found the reason why ...
>I had scheduled the job on another server and generated a SQL script from
>the job.
>Then I installed the package on another SQL server and installed the job
>from the script. The job was running the DTS package on the original SQL
>Server.
>I now understand the encrpted DSTRUN command generated is NOT portable.
>
>"Craig" wrote:
>
>> Hi
>> I have scheduled a DTS package which works fine.
>> The last step in the package is a T-SQL task.
>> I changed the T-SQL task and reran the scheduled job but it ran the original
>> version.
>> I removed the original version but the scheduled job still ran the original
>> version.
>> I restarted SQL Agent and SQL Server but the result is the same.
>>
>> Any suggestions?
>> --
>> Regards,
>> Craig

Relevant Pages

  • SSIS Scheduling Failure - AcquireConnection Error
    ... package into SSIS services in Management Studio and ran the job manually. ... I got the dreaded 'AcquireConnection' error when I tried to schedule ... while logged onto the SQL Server 2005 database server itself. ... the 'SQL Agent Service Account'. ...
    (microsoft.public.sqlserver.dts)
  • Re: Scheduling DTS Packages on 64-bit SQL Server
    ... My understanding is that DTS components are not available for 64-bit SQL ... > I found the following comment on Microsoft's website in regards to scheduling> a DTS package on a 64-bit SQL Server installation. ... do I need> to buy a 32-bit copy of SQL Server to store my packages on to be able to> schedule them? ...
    (microsoft.public.sqlserver.dts)
  • Re: Incorrect DTS package version run by scheduled job
    ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. ... > I would prefer it if the Generate SQL Script option did not generate an> encrypted command line. ... I never use the functionality of right>>>clicking on a package and use the Schedule Package. ...
    (microsoft.public.sqlserver.dts)
  • Re: SSIS job problem
    ... crendials are admins - it would not allow the second admin to ... open / execute / use the package which was encrypted (using first ... Oh - on command line clear text passwords - put the command line into a ... I tried scheduling the package to run as a job step using SQL Agent ...
    (microsoft.public.sqlserver.dts)
  • RE: DTSRUNUI in 2005
    ... At a command prompt: DTSRUN /? ... Also check SQL Server 2000 On-Line Help system. ... I have a DTS package that I can't change that I have exported to a new ...
    (microsoft.public.sqlserver.dts)
Loading