August 13, 2014 at 8:24 pm
I've developed a comprehensive series of packages using SSIS 2012. It's basically one main package that can call out to several child packages.
When I make a change to this "main" package, save my changes in SQL Server Data Tools, and then go to the job in SQL Server Agent and re-run it, it's not picking up on the new changes I've made in the main package.
For example, if I change the text in the main package to have a different subject in an email that the package sends out, the job, when run, still sends the email with the PREVIOUS subject in there. When I look at the contents of this main package file that I've redeployed to my SQL Server, it indeed DOES have the changes made to the email subject, but it's as if those changes aren't there even though I'm staring straight at them when I open the main package file in Notepad.
What am I doing wrong here? This is maddening!
Thanks for any input or suggestions.
August 13, 2014 at 10:24 pm
By chance is that information set by configuration?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
August 14, 2014 at 12:46 am
Which deployment model? How do you deploy?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 14, 2014 at 2:53 am
This post should be in the Integration Services forum rather than Integration Services 2005...since it is about SQL Server 2012 SSIS. 🙂
August 14, 2014 at 8:52 am
I figured this out, although I don't understand why this is the way it is.
I was going into the "View Code" option (this is from memory, but I believe that's it) where you can see all of the code in one window for all of the objects for a package. I made adjustments there and saved this code. When I went back to the individual objects and looked at the code behind those objects via the graphical view of those objects, the changes I'd made in the "Code View" window for the objects were indeed there.
It appears however, that if you don't make those changes to the objects within the graphical view of the objects where you right-click them and click "Edit" and then "Edit Scripts" (I think that's it) to see the code behind the object(s), the changes you've made don't truly "stick". Doesn't make any sense to me but that appears to be the way this works.
Why then do they give us a "View Code" option to see all of the code and actively be able to edit the code if the code truly isn't committed or saved unless you make those changes via the graphical interface of getting to the underlying code that way? Doesn't make sense.
Anyway, thanks for the input here. I know how to get around this going forward it seems.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply