Migrating SSIS from 2005 - 2012?


I am in the process of migrating a SQL server 2005 to a SQL server 2012.     On the 2005 server,  SSIS packages are used to upload CSV data into various databases.  These SSIS packages are created in Visual studio 2005.

My questions are around the versions of software I require on the new server:

1.  Will the new SQL 2012 server require an install of visual studio? if so, which version?  It would only be used for SSIS development - would an express version be suitable?
2. Are there any migrating tools to help?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
>> 1.  Will the new SQL 2012 server require an install of visual studio? if so, which version?  It would only be used for SSIS development - would an express version be suitable?

In SQL Server 2012, BIDS will be called as SQL Server Data Tools with a newer version of Visual Studio.
If you would like to do just SSIS Development, then you can install SQL Server Data Tools and then do your development by connecting to your SQL Server 2005 Server or any other 2012 server as well. No need to install Database Engine Services and hence Express edition not required.

>> 2. Are there any migrating tools to help?

Just open up your existing packages in SSDT and it will guide you through the process while saving it..
Jason YousefSr. BI  DeveloperCommented:
Hi there,
You can use any version of Visual Studio, 12 and Up.  you can use VS 2017 community edition.

but that's only for your development efforts, not for the server.

No migration tool, but remember that SQL 2012 is a totally different animal than 2005!! it uses project deployment, not just single packages like 2005 and 2008.

so you'll need to create an empty project and import your packages into designated projects.  

if you'll currently using package configuration in 2005, you'll need to learn how to use "project parameters"

feel free to ask more questions if you need any links.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.