"Craig HB" <CraigHB@discussions.microsoft.com> wrote in message
news:BCAD3D3F-4BCC-4E4F-8BD9-2BD38A473F11@microsoft.com...
> 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
>

"Craig HB" <CraigHB@discussions.microsoft.com> wrote in message
news:C4064299-DC11-4758-A5AC-101FE45559DC@microsoft.com...
>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.