Re: Incorrect DTS package version run by scheduled job

From: Allan Mitchell (allan_at_no-spam.sqldts.com)
Date: 09/08/04

  • Next message: Scott: "Re: Export Relationships Error" 
    Date: Wed, 8 Sep 2004 21:28:46 +0100

    Which Generate SQL Script?

    If you are referring to the script you get when you Right Click | Schedule a
    DTS package then personally I would use DTSRUNUI to generate a cmdline for
    me. You can then choose to use encrypted or not but as you can see
    encrypted has its drwbacks. 

    -- 
-- 
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know
"Craig" <CraigNicholas@online.nospam> wrote in message
news:0CFE5930-9A01-4577-94DB-A02A33346F47@microsoft.com...
> I would prefer it if the Generate SQL Script option did not generate an
> encrypted command line.
>
> Regards
> Craig
>
> "Darren Green" wrote:
>
> > In message <siprj05t5k56tsn0f1k2b2rgvqn6301dvm@4ax.com>, Sue Hoegemeier
> > <Sue_H@nomail.please> writes
> > >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
> > >
> >
> > I'm with Sue on this one, rarely any need for encrypted command lines.
> > You may find this useful for manually building command lines-
> >
> > Getting Syntax Help for DTSRun
> > (http://www.sqldts.com/default.aspx?301)
> >
> >
> > -- 
> > Darren Green (SQL Server MVP)
> > DTS - http://www.sqldts.com
> >
> > PASS - the definitive, global community for SQL Server professionals
> > http://www.sqlpass.org
> >
> >
  • Next message: Scott: "Re: Export Relationships Error"

    Relevant Pages

    • 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: Incorrect DTS package version run by scheduled job
      ... I had scheduled the job on another server and generated a SQL script from ... The job was running the DTS package on the original SQL ...
      (microsoft.public.sqlserver.dts)
    • Re: Incorrect DTS package version run by scheduled job
      ... encrypted command line. ... >>clicking on a package and use the Schedule Package. ... > I'm with Sue on this one, rarely any need for encrypted command lines. ... > Darren Green (SQL Server MVP) ...
      (microsoft.public.sqlserver.dts)
    • Re: Incorrect DTS package version run by scheduled job
      ... clicking on a package and use the Schedule Package. ... command line can make it difficult to troubleshoot job issues or to ... >I had scheduled the job on another server and generated a SQL script from ...
      (microsoft.public.sqlserver.dts)
    • Re: How to run a DTS package or Stored Procedure from SQL command line
      ... you can use the DTSRUN command to execute the package, ... run the stored procedure. ... > I need to run DTS packages and SPs from SQL command line (WIN command ...
      (microsoft.public.sqlserver.programming)