Hi,

I have a DTS in SQL 2000. It has two steps. One is to delete all the
records in a table. On sucess it then copies the data from a table on
a linked server into a local table.

The DTS runs fine when executed. However when scheduled it only runs
the first step to delete the files and does not move onto the next
step. The history of the job shows that it was a sucess however.
Anybody get any ideas here.

John
johnd (AT) j-dixon (DOT) co.uk

John, I have a similar problem. Have you tried using an odbc connection to
the data in question instead of going through the link? Does the step run
when you execute that one step manually?

Unfortunately for me, I'm not working with a linked server, but using an
odbc connection to an Oracle database in my dts packages. The really weird
thing is that most of the time they run adequately, but sometimes fail for no
known reason.

My particular situation involves pulling data from an Oracle 9database into
SQL Server 2000 -- when the Oracle database was in 8i it worked much faster
for our dts, but the packages weren't much more reliable. When it was
upgraded, the oracle machine was moved to the same facility and it is even is
in the same room as the sql server machine, but the data retrieval has slowed
down substantially and the packages fail more often. We've check the dts
packages and the sql server, and we've checked the Oracle server, and the
firewall... and can't find any errors.

Good luck with your package.

"John D" wrote:

In article <b85e17f2.0409170556.6d68b678 (AT) posting (DOT) google.com>, John D
wrote:
The package may succeed because you did not have enough failures to tip
it over the edge. What I would do is in the package properties hve it
"Fail on first error" and see if the helps you.



--

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

It reacts the same way no matter which connectivity methods I use. I
also tried ticking the fail on first error option but that made no
difference.

It works fine when executed as a DTS. It reacts in this way when
scheduled, only executing the first step but then reporting it as
executed sucessfully.

I have tried different connectivity methods but I still have the same
problem. Also tried fail on first error option but still the same.

If you execute it as a dts package it works fine as it should. It only
responds in this way if you schedule it.



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

OK so the error only happens when scheduled so try this

Wh is the job owned by ?

If == a member of the sysadmin role then log in as the account under which the
SQL Server Agent Service logs in. Now try the package

If != A member of the sysadmin rol then log in as the proxy accunt and try the
package.


--

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