February 9, 2010 at 7:24 am
I have SSIS packages that are ready to be deployed. Currently they are all file packages and to move them to production I would like to 'switch' them to be saved to Sql Server.
How can I do this?
I already created the deployment manifest file through the deployment utility. I'm not sure what step to take next -
In SSMS, should I connect to integration services of the server I need them deployed to, and then import them to the MSDB database (by right-clicking and choosing 'Import Package'?
or is there a step that I'm missing that must be done first?
Any guidance would be helpful, thanks:-)
February 9, 2010 at 7:50 am
Instructions for deployment can be found here: http://msdn.microsoft.com/en-us/library/ms140117.aspx
You'll need to run the deployment manefist from the server you want to deploy to.
Karen
February 9, 2010 at 7:51 am
Look at this blog which explains how to deploy SSIS Packages..
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
February 9, 2010 at 7:55 am
You may also log into Integration Services (in SSMS) navigate to stored packages and right click on MSDB and select Import package and under package location choose file system from the drop down list. You need to provide the package path and package name to be imported as etc..
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
February 9, 2010 at 9:33 am
Thank you.
Is there a difference between doing it this way (importing them into the MSDB database directly) as opposed to the whole deployment utility thing?
February 9, 2010 at 9:38 am
I haven't seen any significant difference. But I am no SSIS expert, both have worked for me..
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply