Hi All,
I am trying to migrate my SQL Server 7.0 server to 2005 on a new box.
I am having trouble migrating the DTS packages. It shows an error, for which I got the solution on Microsoft site as "Installing SQL Server 2000 tools". But My current database is 7.0, is there anything like "SQL Server 7.0 tools"??

- Vishu

__________________
- Vishu

Is it necessary to install these tools, is there no alternative?

- Vishu

Any mods here???

- Vishu

SQL Server 2005 doesn't use DTS although it supports running legacy DTS packages from within the SQL Server Integration Services (SSIS) framework. I suggest you look at SSIS in the 2005 BOL.

--

Joe (Microsoft MVP - XML)

Hey...I am not trying to run the DTS from Legacy...I have migrated them to SSIS and saved as flat files...
Problem is that the DTS I am talking about is connecting to Oracle ...
and it gives me the following error "Unable to case COM object of the type system._comobject to interface type dts.customtask...."

- Vishu

It also says something anout the Oracle Net8 connectivity... whast is that??

- Vishu

Finally it all got solved...the problem was DTS designer package not being installed on the server.
We didnt installed DTS designer on the server but rewrite all the data pump tasks to corresponding Data Flow Tasks in SQL 2005.
With the drivers available with ADO.NET, connectivity to Oracle was never an issue.

- Vishu

DTS to SSIS Migration can be very tedious and time consuming.

I would recommend you to try 3rd party product called DTS xChange. I liked this product very much because... its full Migration package including Discovery, Conversion and Auditing of packages when you run them after migration. It will apply best practices while migrating your packages so if are new to SSIS then this tool will save you significant amount of time.

here is the link

www.dtsxchange.com

Screenshots
http://www.dtsxchange.com/dtsxchange_screenshots.asp

DTS to SSIS Migration FAQs
http://www.dtsxchange.com/help/dtsxc...change.faq.asp