SQL Server Home
SSIS package copy paste data flow task (dft) data viewer issue
6/5/2008 10:48:10 AM
User(s) can reproduce this bug
In BIDS (VS 2005, haven't tried in VS 2008) with SP1 I created a SSIS template package which includes a data flow task with a complete source, row count, split and destination components. I reuse this to setup all of my dimension table package jobs and make a few modifications to some package variables and data flow task items (column names).
What is happening now is that I wanted to add a data viewer to one of the data flow tasks in a package to evaluate the values coming through and the data viewer actually gets added to every single package. If I have lots of packages open it will actually cause VS 2005 to crash. If I only have one package open it will add the data viewer, but it will also add it to all of the other packages in the solution.
When I create a package from my template I copy, paste, and rename the package. I then open up the package and in the properties change the ID to get a new ID value. The thing is that the data flow task in each of the packages has the same guid, so I am assuming this is causing the issue. The data flow task does not appear to be related to the individual package it is embedded in, but somehow they are all related when I try and add the data viewer. Shouldn't the task only be associated with the SSIS package it is embedded in? I can't generate a new guid for the data flow task in the properties window, so I am at a loss right now. Doesn't seem right to me that somehow all of the data flow task are associated with each other, really odd. I can add other items to the data flow task and it doesn't update the other packages, so this appears to be a bug with at least the data viewer.
SQL Server 2005 SP2 - Developer Edition
Integration Services (DTS)
Windows Vista SP1
Operating System Language
Steps to Reproduce
1. create a SSIS package
2. add a data flow task with source, other components, and destination.
3. save the package and then copy and paste it, rename new package
4. change id value of new package in properties window
5. add data viewer in the data flow task of the new package
6. view the original package (if VS did not crash)
data viewer is added to all data flow tasks in the same spot (or removed depending on if you are adding or removing it)
data viewer should only be added to the package being worked on
to post a comment.
Please enter a comment.
on 11/21/2011 at 8:43 AM
I am running SQL Server 2008 R2 and this is still a bug. I have packages that I have copied and pasted controls. Apparently it must be reusing the same GUIDs under the covers because when I try to deploy the packages to SQL server and run it on the server, it jumbles the control flow order all over the place. I ended up going to each package and generating a new ID (just to be safe), then I went into each package and did a CUT / PASTE to have it re-generate a new GUID for each control and it fixed the problem. There are definitely COPY/PASTE issues in SSIS BIDS even in 2008 R2 10.50.1600.1 The control flow works fine if I run it in the debugger, it only goes crazy when I try to run it in SQL Server Mgmt Studio or DTEXEC.
Jeff D. 11/21/2011
on 10/28/2008 at 1:03 PM
Thanks for reporting this problem to us. It has been fixed and will be availabe in our next release.
on 6/13/2008 at 10:13 AM
Thank you for your feedback and support of the SSIS product. This issue doesn’t currently meet the requirements for correction in SQL 2008. We're going to keep it open for triage in the next release.
Again we appreciate your time and support.
to post a workaround.
Please enter a workaround.
on 11/21/2011 at 8:45 AM
Use CUT and PASTE on your control flow controls and data flow controls to fix the conflict ...There are issues with COPY/PASTE in SSIS 2008 R2.
Jeff D. 11/21/2011
© 2014 Microsoft