The Trash Destination and this article came from early experiences of using SSIS and community feedback at the time. When developing a package it is very useful to have a destination adapter that does nothing but consume rows with no setup requirement. You often want run a package part way through development, or just add a path so you can set a Data Viewer. There are stock tasks that can be used, but with the Trash Destination all columns are treated as selected automatically (usage type of read-only), so the pipeline knows they are required. It is also obvious that this is for development or diagnostic purposes, and is clearly not a part of the functional design of the package. It is also ideal for just playing around and exploring concepts in SSIS, and is often used in conjunction with the Data Generator Source. Using these two components it is easy to setup a test of an expression in the Derived Column Transformation for example. The Data Generator Source provides some dummy data, and the Trash Destination allows you to anchor the output path and set a Data Viewer to examine the results.
It can also be used when performance tuning packages. It is a consistent and known quantity that has no external influences, so it is ideal as a destination when breaking the data flow into sections to isolate a bottleneck.
The adapter is really simple to use and requires no setup. Simply drop it onto the pipeline designer and use it to terminate your data flow path.
The component is provided as an MSI file which you can download and run to install it. This simply places the files on disk in the correct locations and also installs the assemblies in the Global Assembly Cache as per Microsoft’s recommendations.
You may need to restart the SQL Server Integration Services service, as this caches information about what components are installed, as well as restarting any open instances of Business Intelligence Development Studio (BIDS) / Visual Studio that you may be using to build your SSIS packages.
Finally, for 2005/2008, you will have to add the transformation to the Visual Studio toolbox manually. Right-click the toolbox, and select Choose Items…. Select the SSIS Data Flow Items tab, and then check the Trash Destination transformation in the Choose Toolbox Items window.
We recommend you follow best practice and apply the current Microsoft SQL Server Service pack to your SQL Server servers and workstations.
Please choose the version to match your SQL Server version. You can install multiple versions and use them side by side if you are developing for multiple versions of SQL Server. For the recent releases of SQL Server Data Tools that can target different versions of SQL Server, please install all target server versions your intend to use.
Trash Destination for SQL Server 2005
Trash Destination for SQL Server 2008
Trash Destination for SQL Server 2012
Trash Destination for SQL Server 2014
Trash Destination for SQL Server 2016
Trash Destination for SQL Server 2017
Trash Destination for SQL Server 2019
SQL Server 2019
Version 22.214.171.124 – SQL Server 2019.
(29 Sep 2019)
SQL Server 2017
Version 126.96.36.199 – SQL Server 2017.
(29 Sep 2019)
SQL Server 2016
Version 188.8.131.52 – SQL Server 2016 GA release.
(25 Jul 2017)
SQL Server 2014
Version 184.108.40.206 – SQL Server 2014 release. Includes upgrade support for 2005, 2008 and 2012 packages to 2014.
(6 Sep 2014)
SQL Server 2012
Version 220.127.116.11 – SQL Server 2012 release. Includes upgrade support for both 2005 and 2008 packages to 2012.
(5 Jun 2012)
SQL Server 2008
Version 18.104.22.168 – SQL Server 2008 release. Includes support for upgrade of 2005 packages. RTM compatible, previously February 2008 CTP.
(4 Mar 2008)
Version 22.214.171.124 – SQL Server 2008 November 2007 CTP.
(14 Feb 2008)
SQL Server 2005
Version 126.96.36.199 – SQL Server 2005 RTM Refresh. SP1 Compatibility Testing.
(12 Jun 2006)
Version 188.8.131.52 – SQL Server 2005 IDW 15 June CTP. Minor enhancements over v184.108.40.206.
(11 Jun 2005)
Version 220.127.116.11 – SQL Server 2005 IDW 14 April CTP. First Public Release.
(30 May 2005)
Make sure you have downloaded the version that matches your version of SQL Server. We offer separate downloads for SQL Server 2005, SQL Server 2008 and SQL Server 2012.
If you an error when you try and use the component along the lines of The component could not be added to the Data Flow task. Please verify that this component is properly installed. … The data flow object "Konesans …" is not installed correctly on this computer, this usually indicates that the internal cache of SSIS components needs to be updated. This is held by the SSIS service, so you need restart the the SQL Server Integration Services service. You can do this from the Services applet in Control Panel or Administrative Tools in Windows. You can also restart the computer if you prefer. You may also need to restart any current instances of Business Intelligence Development Studio (BIDS) / Visual Studio that you may be using to build your SSIS packages.
The full error message is shown below for reference:
TITLE: Microsoft Visual Studio
The component could not be added to the Data Flow task.
Please verify that this component is properly installed.
The data flow object "Konesans.Dts.Pipeline.TrashDestination.Trash, Konesans.Dts.Pipeline.TrashDestination, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b8351fe7752642cc" is not installed correctly on this computer. (Microsoft.DataTransformationServices.Design)
For 2005/2008, once installation is complete you need to manually add the task to the toolbox before you will see it and to be able add it to packages – How do I install a task or transform component? This is not necessary for SQL Server 2012 as the new SSIS toolbox automatically detects components.
If you are still having issues then contact us, but please provide as much detail as possible about error, as well as which version of the the task you are using and details of the SSIS tools installed.