At the moment we have SQL Server 2000 and use DTS to collect data from remote
PCs. These remote PCs connect to our server, load the DTS package locally and
then run the package locally. This is possible because that all have MSDE
installed (which includes DTS.dll).

We are planning on upgrading to SQL Server 2005. As this setup is not
possible with SSIS (we would need a licensed copy of SQL Server 2005 on all
the remote PCs), we will continue to use DTS. I will install the MS SQL
Server 2000 DTS Designer Components (SQL Server 2005 Feature Pack) to do
this.

My question is this: After I replace SQL Server 2000 with SQL Server 2005,
will I still be able to run my DTS packages on remote PCs that only have MSDE
installed.

Thanks,
Craig

If you store your packages as .dtsx files then there will be issues I can
think of.

--


Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com



"Craig HB" <CraigHB (AT) discussions (DOT) microsoft.com> wrote

I won't be storing them as files.

They will be stored on the server (that is being upgraded to 2005). The
remote PCs will run the packages by connecting to the server, loading the
loading the packages in memory (using vb.net code) and then running them
locally.

Will there be issues with that method ?

I might have misinterpreted your answer. Can you give me a bit more details,
please.

You should still be able to retrieve them. There will be on the "2005"
server in msdb a table called sysdtspackages90 and sysdtspackages. The
sysdtspackages should be your 2000 packages.

--


Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com



"Craig HB" <CraigHB (AT) discussions (DOT) microsoft.com> wrote

So if I can retrieve them from those tables, does that mean I can run them
from the remote PCs (which have MSDE) like I'm doing now with 2000.