The ADO.NET destination loads data into a ADO.NET-compliant database that uses a database table or view.
The Azure blob destination writes data to Azure blob storage.
The Azure Data Lake Store destination writes data to an Azure Data Lake Store.
The Cloud destination base model represents both HDFS and Azure Data Lake Store destinations.
The DataReader destination loads dataflow rows into an ADO.NET data reader for consumption by other applications or components.
The DataStreaming destination writes data to DataStreaming Destination.
AstDestinationTransformationNode is the base type that is used for all SQL Server Integration Services dataflow transformations/components in Biml that are destinations (i.e. no non-error output paths).
The Excel destination loads data into Microsoft Excel workbooks.
The Flat File destination writes data to a flat text file in a format specified by a FlatFileFormat definition.
The HDFS destination writes data to a Hadoop cluster.
The ODBC Destination loads data into an ODBC-compliant database that uses a database table, a view, or an SQL command.
The OLE DB destination loads data into an OLE DB-compliant database that uses a database table, a view, or an SQL command.
The Oracle Destination loads data into an Oracle database that uses a database table, a view, or an SQL command. This is done specifically using the Attunity Oracle Connector.
The Raw File destination loads dataflow rows into a raw data file using a file format that is native to this component. This destination and the accompanying source component is intended to improve performance by leveraging the native file format.
The Recordset Destination component creates an in-memory ADO recordset that is stored in a variable.
The Script Component Destination type corresponds directly to a SQL Server Integration Services script component with an input buffer.
The SQL Server PDW destination loads data into a Microsoft SQL Server Parallel Data Warehouse (PDW) appliance. In later versions, PDW is rebranded as the Microsoft Analytics Platform System.
The Teradata Destination loads data into a Teradata database that uses a database table, a view, or an SQL command. This is done specifically using the Attunity Teradata Connector.