A few questions (for Microsoft) regarding upgrade to SQL Server 2005
- For feasibility studies, would SQL Server 2005 Express edition include the
Integration Services (SQL Server 2000 DTS equivalents)?
- Could SQL Server 2000 DTS Packages saved to packaged DTS files be run
against a SQL Server 2005 Database using the existing OLE provider for SQL
Server 2000 with no DTS modifications, using the SQL 2000 client util
(DTSRUN.exe) [on an interim basis]?
- Does SQL Server 2005 include DTSRUN.exe for running SQL Server 2000 DTS
packaged DTS files, or would existing DTS have to be "packaged" into .NET SQL
server 2005 Integration Services?

"Patrick" <patl (AT) reply (DOT) newsgroup.msn.com> wrote

No.
http://www.microsoft.com/sql/prodinf...-features.mspx

Yes.

From

SQL Server 2005 Upgrade Handbook

Note that you'll have time to incrementally migrate packages over to SSIS.
When you install SQL Server 2005, you have the option to install the runtime
files required for DTS packages to execute on SQL Server 2005-without SQL
Server 2000 needing to be installed. This makes the side-by-side migration a
compelling story, especially in an environment where the DTS packages
contain many tasks that require manual migration. SSIS also contains an
Execute DTS package object when the runtime files or SQL Server 2000 has
been installed on the SSIS server. A side-by-side implementation of SQL
Server 2005 SSIS and SQL Server 2000 DTS will give you the greatest
flexibility as you approach package migration.
http://www.microsoft.com/technet/pro.../sqlupgrd.mspx

David

I have reviewed,
http://www.microsoft.com/technet/pro...grd.mspx#E1CAC

A bit confused by "you have the option to install the runtime
files required for DTS packages to execute on SQL Server 2005-without SQL
Server 2000 needing to be installed"

Currently we have
1) ServerA
-- WIndows 2003 server
-- SQL SErver 2000 client utils including DTSRun.exe
-- Saved DTS package files

2) Server B
-- Windows 2003 server
-- SQL Server 2000
-- (this is the current target server for the data-pumping DTS packages that
reside on Server A)


Question
1) When Server B is upgraded to SQL Server 2005, could the DTS on Server A
be run against SQL Server 2005 on Server B using SQL Server 2000's DTSrun.exe?

2) All my DTS's second "step" currently is self-configuring other task
step's properties based on environment variables read in a step 1. Would
the upgrade wizard simply abort?

3) The Microsoft articule suggests that the upgrade wizard are not that good
at handling "transformation" and it will revert to invoking the
Transformation step in the old DTS package?? Is it only if i use VBSCript
for transformation or could it not even handle straight-forward pre-defined
transformation like TRimming?


"David Browne" wrote:

"Patrick" <patl (AT) reply (DOT) newsgroup.msn.com> wrote

I believe so. Here Server A is just a client of Server B.

I don't know what the upgrade wizard will do with it. But the big picture
is that to move to SSIS you will need to rewrite your DTS packages. The
upgrade wizard may make this easier, but it's still a rewrite. Package
configuration and customization in DTS is really painful and bad. This is
something you'll definitely want to replace in SSIS. So you might just
delete this step prior to upgrading and replace it with the new SSIS
functionality.

Again. You can continue to run your existing DTS packages until you are
finished rewirting them in SSIS.

David