Migrated stored SSIS packages in msdb from SQL 2005 to 2012

[Luvsql]

We have a few SSIS packages that were setup in the msdb database. There are no package files as they were created by someone else. I've tried the 2012 upgrade advisor on our new SQL 2012 server but supposedly to check for any issues, it requires that SQL 2005 SSIS be installed on the new server, which we can't do.

So, if we don't have the source files to open in Visual Studio then save as a new version, can we not migrate what's in MSDB to sql 2012? I'm confused if it's in the database and does not rely on any files, why it can't just be migrated.

 

[fredericofonseca]

I would export those packages to filesystem and then use the normal upgrade advisor - that should not require the old 2005 SSIS install

Once upgraded you may or not move them up to the msdb

Regards

Frederico Fonseca
SysSoft Integrated Ltd

http://www.syssoft-int.com

FAQ219-2884
FAQ181-2886

 

[xlbo]

yep - use SSMS and choose the Integration Services type connection
From there, right click on a package and choose "Export"
Chnage options to file system and export to a file location
From there you can add existing item to a vis studio solution and go from there

Rgds, Geoff

We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.

Please read FAQ222-2244 before you ask a question

 

[SQLBill]

Check out this link for another option:

http://www.databasejournal.com/feat...o-copy-SSIS-packages-stored-in-SQL-Server.htm

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875