dbTalk Databases Forums  

Incorrect DTS package version run by scheduled job

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Incorrect DTS package version run by scheduled job in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Craig
 
Posts: n/a

Default Incorrect DTS package version run by scheduled job - 09-07-2004 , 05:19 AM






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

Reply With Quote
  #2  
Old   
Sue Hoegemeier
 
Posts: n/a

Default Re: Incorrect DTS package version run by scheduled job - 09-07-2004 , 11:53 AM






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 (AT) online (DOT) nospam> wrote:

Quote:
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


Reply With Quote
  #3  
Old   
Darren Green
 
Posts: n/a

Default Re: Incorrect DTS package version run by scheduled job - 09-07-2004 , 02:49 PM



In message <siprj05t5k56tsn0f1k2b2rgvqn6301dvm (AT) 4ax (DOT) com>, Sue Hoegemeier
<Sue_H (AT) nomail (DOT) please> writes
Quote:
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



Reply With Quote
  #4  
Old   
Craig
 
Posts: n/a

Default Re: Incorrect DTS package version run by scheduled job - 09-08-2004 , 02:35 AM



I would prefer it if the Generate SQL Script option did not generate an
encrypted command line.

Regards
Craig

"Darren Green" wrote:

Quote:
In message <siprj05t5k56tsn0f1k2b2rgvqn6301dvm (AT) 4ax (DOT) com>, Sue Hoegemeier
Sue_H (AT) nomail (DOT) 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



Reply With Quote
  #5  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Incorrect DTS package version run by scheduled job - 09-08-2004 , 03:28 PM



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 (AT) online (DOT) nospam> wrote

Quote:
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 (AT) 4ax (DOT) com>, Sue Hoegemeier
Sue_H (AT) nomail (DOT) 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





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.