January 22, 2015 at 11:36 am
Hello, all. I'm fairly new to SSIS. I created a package (SQL 2005) that works great, then scheduled its execution using the following process:
* Import package from File System to MSDB via Integration Services (with appropriate protection level)
* Created SSIS SQL job using SSIS Package Store referencing package added to MSDB in previous step
That's it. Works great every day.
However, when I modify the SSIS package in BIDS, the changes aren't included in the executed SQL job. What is the proper process to have my scheduled job execute my newly updated SSIS package? Do I need to drop it from MSBD and re-add? Any info appreciated.
January 22, 2015 at 4:06 pm
Just save the job back to MSDB after making your changes. Making changes in BIDS and saving it locally won't update the scheduled job.
January 22, 2015 at 4:14 pm
Can you elaborate briefly on how exactly that should be done? In SSMS, when logged in to Integration Services, my package is already in MSDB. I can drop and re-create it, but don't see how to basically refresh it. This is my main point of confusion. Any clarification appreciated. Sorry if I'm missing the obvious.
January 22, 2015 at 5:06 pm
Eh well the same way you originally saved it to the DB, it should prompt you if you want to overwrite it and you just click yes.
I think there's ways to set up visual studio to automatically upload projects to the DB but I'm not an expert on that.
January 23, 2015 at 2:48 am
SmackMule (1/22/2015)
Can you elaborate briefly on how exactly that should be done? In SSMS, when logged in to Integration Services, my package is already in MSDB. I can drop and re-create it, but don't see how to basically refresh it. This is my main point of confusion. Any clarification appreciated. Sorry if I'm missing the obvious.
If you download BIDSHelper (http://bidshelper.codeplex.com/) then you can simplify the deployment process from BIDS to MSDB. See here: http://bidshelper.codeplex.com/wikipage?title=Deploy%20SSIS%20Packages&referringTitle=Documentation
February 28, 2015 at 5:21 pm
Hi,
Do follow the below steps.
Integration services--> Right click the package which you created under MSDB folder.
then select import package.--> select package location as file system--> then select a latest package(last modified) in the package path..
then it will ask overwrite a package in existing package name. give yes.
run a job. it will work.
thanks,
Kannan vignesh.
February 28, 2015 at 10:51 pm
Thank you! This is good info. Love having more options.
March 2, 2015 at 3:18 pm
SSIS has a deployment utility to help with these sort of things. Right click your project name at the top in BIDS > properties > deployment utility.... set CreateDeploymentUtility = true. Next build the package.
Then inside the project's windows directory, a bin\deployment folder will be created along with a manifest file. Move these contents to the machine you want to deploy your updated package to and follow the wizard prompts after running the manifest file on that machine.
----------------------------------------------------
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply