April 4, 2011 at 10:18 am
I have a simple package that is simply trying to read in data from one DB and move specific items from a table to second DB/table with a bit of massaging in the middle. Initially, I had a script task component as the entry point for the package to set a "LoadID" variable. After completing the package and running it successfully I realized the initial script task was not needed. So, I removed it; ie. right click, and selected delete. A subsequent run hung the package - turned all the components yellow but didn't finish - odd behavior considering I had removed all references to the variable the script task had created; ie. LoadID. Um, since the script task didn't really cause any overhead I put it back in. Now I get an error that tells me that it can't find the component. The question is this, when a script task is removed, is there special considerations for its removal even though the only thing its doing is creating a global variable named "LoadID"?
Thanx.
Ed.
April 4, 2011 at 12:45 pm
No special considerations but it sounds like all references weren't removed. Is there a package variable or environment variable that was dependent on the task?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
April 4, 2011 at 1:45 pm
I thought of that as well but no. It gave me the guid of the component in the error message that it couldn't be found. Strange to me. I haven't developed a lot of packages - in fact just a couple of relatively easy xformations and would have thought if a component were removed that VS would remove all references. I took a look at the "code view" - the xml - and sure enuf, there it was; spattered randomly throughout the xml about a dozen times.
appreciate your reply - i've set it aside for now. thought i'd get back to it when i rec'vd some replies and suggestions.
Thanx.
ed.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply