OK
DTS is a client application so DTS will look for resources in relation to
the place of execution. When you are sat on your PC in EM and open a
package on the server then the package is no longer at the server it is at
your PC. When a DTS package is scheduled then it executes on the scheduling
server.
Resources then are in relation to the executing box and it may be that the
server takes longer to retrieve those resources than you do from your PC.
--
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
[quoted text, click to view] "Martin" <mdeslandes@ratiopharm.ca> wrote in message
news:uUG9KUj2EHA.2112@TK2MSFTNGP15.phx.gbl...
> Hi,
> Since 2 weeks, we have a problem with SQL Server 2000. We have defined
> a
> schedule job in witch we execute about 100 dts packages. This job usually
> take about 2h30 to run but since 2 weeks, it takes about 8 hours. I've
> noticed that if I execute a particular step on the server, it takes 1h30
> to
> run. And if I connect to the server by enterprise manager and I start the
> DTS package on the server from my PC, it takes 20 minutes (witch is the
> normal time to run). We have installed MDAC 2.8 on the server 2 weeks ago,
> so I thought this was the problem, but I successfully rollback the version
> of MDAC to 2.7 using the dasetup.exe /u command and we still have the
> problem.
>
> Thanks in advance,
> Martin
>
> Server configuration:
>
> Windows 2000 server sp4
> SQL server 2000 Enterprise sp3
> Office 2000
>
>