|
|
You're in the
sql server dts
group:What's the pitfall of copy/paste a SSIS package
sql server dts:
exisiting package. I generated a new ID on package level for the copied package (but other level objects still share the same ID ), then I made some modification on the new package, and let two packages run in parallel in a master package, which caused tasks cross-run each other. Is this because those tasks share the same IDs? If so, what' s the easiest way to make the pasted package have different IDs on all objects from the existing one? Thanks,
Hello yongli,
Are you saying that after having changed the PackageID for one of the packages you had issues? What were those issues exactly? How did they cross over? Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com [quoted text, click to view] > When I copy/paste an existing package, it inherits all the IDs from > the exisiting package. I generated a new ID on package level for the > copied package (but other level objects still share the same ID ), > then I made some modification on the new package, and let two packages > run in parallel in a master package, which caused tasks cross-run each > other. Is this because those tasks share the same IDs? If so, what' > s the easiest way to make the pasted package have different IDs on all > objects from the existing one? > > Thanks, >
Hi Allan,
I did change the package ID. The reason I copied/pasted an existing package to create a new one is because they have the same steps except for details. I saw this oddity in the debug mode. Although I changed the package IDs, but the other objects still share the same ID between two packages (I am wondering if this is the root cause). Both Packages run some Data Flow Tasks and SQL validations. The first one did 140 rows, and the second one did 7 rows. This is what I observed: when I put both packages in a master package and let them run in parallel (later I found putting a dependency between them still cause the problem), The 7 rows package finish successful in Green in Master package while the other is still running some DFT task, I can see the correponsding task in yellow in the successful package, kind of odd? At end the other package failed in red in Master Package, the corresponding tasks in the successful package changed color to red too even it is green in the master package, also the row count changed from 7 to 140 something. It seems to me this is some synchroniztion problem in display in the debug mode. (maybe due to those tasks with same IDs). Although I checked the results to be fine, but this will affect my overal ETL flow in the master package. This is why I asked if we need to change all the object IDs in this case? Thanks. [quoted text, click to view] "Allan Mitchell" wrote:
> Hello yongli, > > Are you saying that after having changed the PackageID for one of the packages > you had issues? What were those issues exactly? How did they cross over? > > > > > Allan Mitchell > www.SQLDTS.com > www.SQLIS.com > www.Konesans.com > > > When I copy/paste an existing package, it inherits all the IDs from > > the exisiting package. I generated a new ID on package level for the > > copied package (but other level objects still share the same ID ), > > then I made some modification on the new package, and let two packages > > run in parallel in a master package, which caused tasks cross-run each > > other. Is this because those tasks share the same IDs? If so, what' > > s the easiest way to make the pasted package have different IDs on all > > objects from the existing one? > > > > Thanks, > > > >
Hello yongli,
I do not think that this will be an issue. new Package IDs should be sufficient. Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com [quoted text, click to view] > Hi Allan, > > I did change the package ID. The reason I copied/pasted an existing > package to create a new one is because they have the same steps except > for details. > > I saw this oddity in the debug mode. Although I changed the package > IDs, > but the other objects still share the same ID between two packages (I > am > wondering if this is the root cause). Both Packages run some Data > Flow Tasks > and SQL validations. > The first one did 140 rows, and the second one did 7 rows. This is > what I > observed: > when I put both packages in a master package and let them run in > parallel > (later I found putting a dependency between them still cause the > problem), > The 7 rows package finish successful in Green in Master package while > the > other is still running some DFT task, I can see the correponsding task > in > yellow in the successful package, kind of odd? > At end the other package failed in red in Master Package, the > corresponding > tasks in the successful package changed color to red too even it is > green in > the master package, also the row count changed from 7 to 140 > something. > It seems to me this is some synchroniztion problem in display in the > debug > mode. > (maybe due to those tasks with same IDs). > Although I checked the results to be fine, but this will affect my > overal ETL flow in the master package. This is why I asked if we need > to change all the object IDs in this case? > > Thanks. > > "Allan Mitchell" wrote: > >> Hello yongli, >> >> Are you saying that after having changed the PackageID for one of the >> packages you had issues? What were those issues exactly? How did >> they cross over? >> >> Allan Mitchell >> www.SQLDTS.com >> www.SQLIS.com >> www.Konesans.com >>> When I copy/paste an existing package, it inherits all the IDs from >>> the exisiting package. I generated a new ID on package level for >>> the copied package (but other level objects still share the same ID >>> ), then I made some modification on the new package, and let two >>> packages run in parallel in a master package, which caused tasks >>> cross-run each other. Is this because those tasks share the same >>> IDs? If so, what' s the easiest way to make the pasted package have >>> different IDs on all objects from the existing one? >>> >>> Thanks, >>>
One more thing to add in my case. I have a variable defined in both package,
when runing separately, it is fine. When running in paralle, one of the later finished package failed due to follwoing reason: Error: The script threw an exception: The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on a container during execution of the package and the element is not there. [quoted text, click to view] "yongli" wrote:
> Hi Allan, > > I did change the package ID. The reason I copied/pasted an existing package > to create a new one is because they have the same steps except for details. > > I saw this oddity in the debug mode. Although I changed the package IDs, > but the other objects still share the same ID between two packages (I am > wondering if this is the root cause). Both Packages run some Data Flow Tasks > and SQL validations. > The first one did 140 rows, and the second one did 7 rows. This is what I > observed: > when I put both packages in a master package and let them run in parallel > (later I found putting a dependency between them still cause the problem), > The 7 rows package finish successful in Green in Master package while the > other is still running some DFT task, I can see the correponsding task in > yellow in the successful package, kind of odd? > At end the other package failed in red in Master Package, the corresponding > tasks in the successful package changed color to red too even it is green in > the master package, also the row count changed from 7 to 140 something. > It seems to me this is some synchroniztion problem in display in the debug > mode. > (maybe due to those tasks with same IDs). > > Although I checked the results to be fine, but this will affect my overal > ETL flow in the master package. This is why I asked if we need to change all > the object IDs in this case? > > Thanks. > > > "Allan Mitchell" wrote: > > > Hello yongli, > > > > Are you saying that after having changed the PackageID for one of the packages > > you had issues? What were those issues exactly? How did they cross over? > > > > > > > > > > Allan Mitchell > > www.SQLDTS.com > > www.SQLIS.com > > www.Konesans.com > > > > > When I copy/paste an existing package, it inherits all the IDs from > > > the exisiting package. I generated a new ID on package level for the > > > copied package (but other level objects still share the same ID ), > > > then I made some modification on the new package, and let two packages > > > run in parallel in a master package, which caused tasks cross-run each > > > other. Is this because those tasks share the same IDs? If so, what' > > > s the easiest way to make the pasted package have different IDs on all > > > objects from the existing one? > > > > > > Thanks, > > > > > > >
Hello yongli,
The error suggests that you are trying to ref an object that the task knows nothing about. Is it a script task that throws the error? How do you let the task know about the variable? What is the code you use? Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com [quoted text, click to view] > One more thing to add in my case. I have a variable defined in both > package, when runing separately, it is fine. When running in paralle, > one of the later finished package failed due to follwoing reason: > > Error: The script threw an exception: The element cannot be found in a > collection. This error happens when you try to retrieve an element > from a collection on a container during execution of the package and > the element is not there. > > "yongli" wrote: > >> Hi Allan, >> >> I did change the package ID. The reason I copied/pasted an existing >> package to create a new one is because they have the same steps >> except for details. >> >> I saw this oddity in the debug mode. Although I changed the package >> IDs, >> but the other objects still share the same ID between two packages (I >> am >> wondering if this is the root cause). Both Packages run some Data >> Flow Tasks >> and SQL validations. >> The first one did 140 rows, and the second one did 7 rows. This is >> what I >> observed: >> when I put both packages in a master package and let them run in >> parallel >> (later I found putting a dependency between them still cause the >> problem), >> The 7 rows package finish successful in Green in Master package while >> the >> other is still running some DFT task, I can see the correponsding >> task in >> yellow in the successful package, kind of odd? >> At end the other package failed in red in Master Package, the >> corresponding >> tasks in the successful package changed color to red too even it is >> green in >> the master package, also the row count changed from 7 to 140 >> something. >> It seems to me this is some synchroniztion problem in display in the >> debug >> mode. >> (maybe due to those tasks with same IDs). >> Although I checked the results to be fine, but this will affect my >> overal ETL flow in the master package. This is why I asked if we >> need to change all the object IDs in this case? >> >> Thanks. >> >> "Allan Mitchell" wrote: >> >>> Hello yongli, >>> >>> Are you saying that after having changed the PackageID for one of >>> the packages you had issues? What were those issues exactly? How >>> did they cross over? >>> >>> Allan Mitchell >>> www.SQLDTS.com >>> www.SQLIS.com >>> www.Konesans.com >>>> When I copy/paste an existing package, it inherits all the IDs from >>>> the exisiting package. I generated a new ID on package level for >>>> the copied package (but other level objects still share the same ID >>>> ), then I made some modification on the new package, and let two >>>> packages run in parallel in a master package, which caused tasks >>>> cross-run each other. Is this because those tasks share the same >>>> IDs? If so, what' s the easiest way to make the pasted package >>>> have different IDs on all objects from the existing one? >>>> >>>> Thanks, >>>>
I used script task component and specified the variable in package level and
ReadOnlyVariables property in the script task Editor. Since I copied and pasted the packages so the script task ID remained same in both packages, as I said I could run each package individaully without problem, but only when I ran them in parallel, it got the error. This behavior is consistent with the colorring changing problem described earlier when I ran the pacakges in parallel, that is SSIS tends to display the object with same ID in same color, this might be the pitfall in copying/pasting a SSIS package. [quoted text, click to view] "Allan Mitchell" wrote:
> Hello yongli, > > The error suggests that you are trying to ref an object that the task knows > nothing about. Is it a script task that throws the error? How do you let > the task know about the variable? What is the code you use? > > > Allan Mitchell > www.SQLDTS.com > www.SQLIS.com > www.Konesans.com > > > One more thing to add in my case. I have a variable defined in both > > package, when runing separately, it is fine. When running in paralle, > > one of the later finished package failed due to follwoing reason: > > > > Error: The script threw an exception: The element cannot be found in a > > collection. This error happens when you try to retrieve an element > > from a collection on a container during execution of the package and > > the element is not there. > > > > "yongli" wrote: > > > >> Hi Allan, > >> > >> I did change the package ID. The reason I copied/pasted an existing > >> package to create a new one is because they have the same steps > >> except for details. > >> > >> I saw this oddity in the debug mode. Although I changed the package > >> IDs, > >> but the other objects still share the same ID between two packages (I > >> am > >> wondering if this is the root cause). Both Packages run some Data > >> Flow Tasks > >> and SQL validations. > >> The first one did 140 rows, and the second one did 7 rows. This is > >> what I > >> observed: > >> when I put both packages in a master package and let them run in > >> parallel > >> (later I found putting a dependency between them still cause the > >> problem), > >> The 7 rows package finish successful in Green in Master package while > >> the > >> other is still running some DFT task, I can see the correponsding > >> task in > >> yellow in the successful package, kind of odd? > >> At end the other package failed in red in Master Package, the > >> corresponding > >> tasks in the successful package changed color to red too even it is > >> green in > >> the master package, also the row count changed from 7 to 140 > >> something. > >> It seems to me this is some synchroniztion problem in display in the > >> debug > >> mode. > >> (maybe due to those tasks with same IDs). > >> Although I checked the results to be fine, but this will affect my > >> overal ETL flow in the master package. This is why I asked if we > >> need to change all the object IDs in this case? > >> > >> Thanks. > >> > >> "Allan Mitchell" wrote: > >> > >>> Hello yongli, > >>> > >>> Are you saying that after having changed the PackageID for one of > >>> the packages you had issues? What were those issues exactly? How > >>> did they cross over? > >>> > >>> Allan Mitchell > >>> www.SQLDTS.com > >>> www.SQLIS.com > >>> www.Konesans.com > >>>> When I copy/paste an existing package, it inherits all the IDs from > >>>> the exisiting package. I generated a new ID on package level for > >>>> the copied package (but other level objects still share the same ID > >>>> ), then I made some modification on the new package, and let two > >>>> packages run in parallel in a master package, which caused tasks > >>>> cross-run each other. Is this because those tasks share the same > >>>> IDs? If so, what' s the easiest way to make the pasted package > >>>> have different IDs on all objects from the existing one? > >>>> > >>>> Thanks, > >>>> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |