I have many DTS packages. I modified them to accommodate new connections with
different login information. They work fine when executed from DTS packages.
All these packages used to be executed from SQL scheduler and they been fine
until my changes. After my above described changes to the packages some of
them continue to be successfully run from scheduler but some of them randomly
failed. This problem can be fixed if I will recreate schedule jobs from
scratch (confirmed).
Can anyone give an advice is it possible to eliminate recreating jobs to be
able to run the updated login information packages successfully?
Would it work if I will script the same job from the different server (with
old connection information) and run on this server( with new connection)?

Thanks,
Ilin

--
Message posted via http://www.sqlmonster.com

So when you recreate the jobs it is fine?>
What does your job string look like for DTSRUN? LIke this DTSRUN
~/Z28473469743659276.....

If yes then this stores all the parameters you need to run the package
encrytped and if you change the package at all it will still execute the
version it is looking at and not the new version.


--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"Ilin Star via SQLMonster.com" <forum (AT) SQLMonster (DOT) com> wrote