It's been a few years since I dealt with the DTS 2000/ SQL 2005 issues, so
take this advice with cautious optimism:
If you have downloaded and installed the SQL 2005 Legacy Components (should
also be on the install medial) you should be able to manage, edit, and run
older DTS packages from SQL 2005. (In SSMS, look under Management >> Legacy
Post by amacData Transformation Services)
To schedule the package, create a stored procdure wrapper that executes the
package, then schedule that SP from SQL Agent. (Sorry, I don't remember the
T-SQL syntax for executing DTS.)
A remote user could invode the stored procedure, start the job, or even run
the DTS Package. The first two should run under the context of the server,
and for the third, the user would need the legacy components installed.
HTH
=====
Todd C
Post by amac1. How can you shedule DTS-Packages in SQL2005?
2. When you have created dtsx packages on a server, is it possible for a
user to run that package from this own machine?