Please start any new threads on our new site at http://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2008 Forums
 SSIS and Import/Export (2008)
 Migrating packages to IS
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

JaybeeSQL
Posting Yak Master

112 Posts

Posted - 01/30/2014 :  07:29:19  Show Profile  Reply with Quote
Hi all,

We have an upcoming requirement to upgrade packages on about 11 db's from DTS, I know the Upgrade Advisor only has a 10-15% success rate for more complex packages, so effectively we are looking at recreating them.

I have no meaningful experience with DTS, but from what I can gather, many of the packages have a dozen or more steps.

We have a checklist in place for the underlying migration (2K-2K8), but I'd like to get an overview of the steps we need to undertake for the IS portion.

Thanks,

J B

visakh16
Very Important crosS Applying yaK Herder

India
52326 Posts

Posted - 02/03/2014 :  06:50:28  Show Profile  Reply with Quote
In my experience we had to rewrite almost every packages (baring very few simple ones!) while moving to SSIS from DTS as basic architecture of SSIS itself is different from DTS

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/
https://www.facebook.com/VmBlogs
Go to Top of Page

JaybeeSQL
Posting Yak Master

112 Posts

Posted - 02/04/2014 :  07:45:46  Show Profile  Reply with Quote
Hi Visakh, thanks for the input.

I have done a quick sample audit of the packages, typically they involve any combination of the below;

1) Deletion of existing files,
2) Running a SQL statement or batch file,
3) Connecting to a SQL/Excel source/destination, importing or exporting data to or from it;
4) Sending emails indicating which of the previous elements failed, or overall success.


There are several packages containing ActiveX Scripting, though they SEEM only to either check whether a csv/txt file exists, rename it, or make a copy of it to a network drive and delete the original.

What transformations in SSIS will I need to create the packages?

Thanks,

JB
Go to Top of Page

JaybeeSQL
Posting Yak Master

112 Posts

Posted - 02/04/2014 :  07:46:37  Show Profile  Reply with Quote
BTW I have not noticed any explicit data conversions.
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.08 seconds. Powered By: Snitz Forums 2000