Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Migrate SSIS package from 2005 to 2017

$
0
0
Hi.  I'm in the process of migrating a SQL instance off of 2005 to 2017.  One of the existing SQL 2005 Agent jobs calls a SSIS package that is stored in MSDB.  I exported the package and brought it into Visual Studio on the 2017 server to inspect it for any hard-coded references to servers, drive letters, etc.  I saved the package to the file system and imported it into the MSDB hive in Integration Services 14.0.  Can I just have the Agent job run the package from MSDB on the 2017 server like on the 2005 server, or do I have to create a Integration Services Catalog?  The package functionality is simple; it doesn't need features of the Integration Services Catalog like configurations or parameters.  Thanks.

Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>