InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 08:47:27 GMT20http://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxIf you just want to run the packages on the new server:Export your DTS packages using DTSBackup.Save them to a network locationCreate an SSIS job that calls the DTS packages.JamieWed, 04 May 2011 22:38:53 GMTJamie Ingram-729524http://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxSee if this helps you since it helped me. Specifically, I used the Package Migration wizard so click that link in thisdocument to see if it helps you too.http://msdn.microsoft.com/en-us/library/ms143496.aspxTue, 03 May 2011 10:14:15 GMTrobert.wileyhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxTry to install the backward compatability on sql server 2005,you can able to see the DTS packages in the 2005.Tue, 15 Jun 2010 13:01:41 GMTkissingharryhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxif you dont/wont need to make any changes to the packages, use DTS Backup 2000 application (http://www.sqldts.com/242.aspx) and run the DTS in legacy mode on the 2005 server. Otherwise I'd use one of the many DTS Documentation tools and generate documentation for all my DTS packages. Then I'd sit down and start with number one and create an equivalent SSIS package until I'd done them all. Depending on your specific situation, there may be a shortcut/easier way to do it, but in my experience, you just have to end up rebuilding them all anyway.Cheers and Good luck.Wed, 27 Jan 2010 10:32:06 GMTbradfordshultzhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxI learnt the hard way that importing existing packages was no short cut. By the time it was all up and running I wished we had rebuilt everything from scratch. Especially since a lot of the packages could have easily been replicated with some meta data and a looping container!The barrier to this was that the existing DTS packages were "proven to work" and our project managers liked this, unfortunately the logic was flawed because they were not proven to work within SSIS. And in many cases they didn't! This route proved to be a massive false economy. Obviously your situation may be entirely different, but I wish we had re-done the bulk of our packages - even if it had just been the more straight forward data shunting tasks.Wed, 09 Dec 2009 09:33:29 GMTjezmanhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxthanks, gud ideaTue, 08 Dec 2009 08:57:10 GMTsureshdeenuhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxTry Using DTSBACKUP TOOLTue, 08 Dec 2009 03:49:05 GMTSree Arjun Divhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxhi!!try that:1-make a backup of your msdb db.2-restore it on your target server with another name(be carful!!!, don't overwrite on the true msdb on sql 2005)3-excecute that in the msdb that you've restored:use msdb_restoredgoinsert into msdb.dbo.sysdtspackagesselect * from sysdtspackages awhere name in ('dts names....')and createdate =(select max(createdate)from sysdtspackages bwhere b.name in ('dts names....')and a.name=b.name)enjoy!!!Mon, 07 Dec 2009 06:35:09 GMTnba ninetytwohttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxI tried to move each dts package, rt. click on it-> Open -> Save as storagefile on source server(2000)On the destination server(2005), rt click on DTS package folder-> Import -> select the dts package storage file from the shared folder. But i couldnt open the package in destination server. wht is the best sollution for me?Sun, 06 Dec 2009 16:09:02 GMTsureshdeenuhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxcan u pls give me step by step to copy the packages from sql 2000 to 2005Sun, 06 Dec 2009 16:01:42 GMTsureshdeenuhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspx[quote][b]sureshdeenu (12/5/2009)[/b][hr]Hi I am trying to copy DTS Packages from sql 2000 to 2005? what is the process i can do it?[/quote]As I recall, you can export & import them one at a time, or try the tools mentioned above.Sun, 06 Dec 2009 08:23:46 GMThomebrew01http://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxHi I am trying to copy DTS Packages from sql 2000 to 2005? what is the process i can do it?Sat, 05 Dec 2009 20:23:17 GMTsureshdeenuhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxAre you wanting to import and convert to SSIS at the same time ? The tool I referred to just imports them as DTS running in Legacy mode.Sat, 05 Dec 2009 12:12:28 GMThomebrew01http://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxYes, there are tools available. With our dts packages we see about a 50% conversion failure rate and have to manually do the conversion anyway.One such tool that can do conversions[url]http://www.pragmaticworks.com/products/Business-Intelligence/dtsxchange/[/url]ssis tutorial[url]http://bi-polar23.blogspot.com/2008/03/new-to-ssis-start-here.html[/url]Conversion Article[url]http://www.sqlmag.com/Article/ArticleID/94095/sql_server_94095.html[/url]Sat, 05 Dec 2009 10:22:04 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxI think I used "DTSBackup2000" tool. Free download, and pushed 100+ DTS packages from 2000 to 2005 with just a few clicks.Fri, 04 Dec 2009 22:43:01 GMThomebrew01http://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxyes i need all the packages.Fri, 04 Dec 2009 18:31:23 GMTcharipghttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxSince it is not guaranteed that all of the packages will properly convert, you will need to investigate the packages at the individual level. Are you sure that you will even need all 150 packages? Are any of them deprecated?Hunker down and just start doing it.Fri, 04 Dec 2009 17:28:15 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic829138-146-1.aspxHi,I need to import 150 DTS packages in sqlserver2005.Importing one by one shouls take lot of time. how to import all these packages at a time.can you please provide the query.Thanks in advance.Fri, 04 Dec 2009 11:38:57 GMTcharipg