Hello ,
Just to add to Paul's reply. It is also my expereince that a migration is
difficult for the wizard if there is any level of complexity but also even
if the package IS migrated successfully the wizard really has no way of doing
things in the best way. Take Looping for instance. In DTS we did this through
code but in SSIS we do this using one of the lopping constructs we have now
in the control flow. there is no real way the wizard can convert your code
into the SSIS equivalent.
I tend to leave 2K packages as they are and they will execute happily in
2K5. I then hand-migrate in slow time. This way I get an optimal package.
--
Allan Mitchell
http://wiki.sqlis.com |
http://www.sqlis.com |
http://www.sqldts.com |
http://www.konesans.com [quoted text, click to view] > You can start the Package Migration wizard from the Management,
> Legacy, Data
> Transformation Services folder by right-clicking. The wizard will
> allow you
> to select multiple packages in one go. I'd recommend reading up on the
> upgrade process in as many places as possible - there's plenty of info
> on the
> web for this eg
>
http://www.simple-talk.com/sql/sql-server-2005/dts-to-ssis-migration/. > In my
> experience a package with any level of complexity won't migrate
> correctly/completely. UDL files and ActiveX script transformations are
> just 2
> cases which caused major problems for us. Thinking more widely about
> this
> process, I found that a normal migration is the least attractive
> option and
> in the end preferred to create the SSIS packages from scratch. This
> way I
> take advantage of the new tasks and components, logging, indirect
> configuration etc which makes the process worthwhile - just my 2ps
> worth.
> HTH,
> Paul Ibison