Lesson 1-7: Add and configure the OLE DB destination
Your package can now extract data from the flat file source and transform that data into a format compatible with the destination. The next task is to load the transformed data into the destination. To load the data, you add an OLE DB destination to the data flow. The OLE DB destination can use a database table, view, or a SQL command to load data into a variety of OLE DB-compliant databases.
In this task, you add and configure an OLE DB destination to use the OLE DB connection manager that you previously created.
Add and configure the sample OLE DB destination
In the SSIS Toolbox, expand Other Destinations, and drag OLE DB Destination onto the design surface of the Data Flow tab. Place the OLE DB Destination directly below the Lookup Date Key transformation.
Select the Lookup Date Key transformation and drag its blue arrow over to the new OLE DB Destination to connect the two components together.
In the Input Output Selection dialog, in the Output list box, select Lookup Match Output, and then select OK.
On the Data Flow design surface, select the name OLE DB Destination in the new OLE DB Destination component, and change that name to Sample OLE DB Destination.
Double-click Sample OLE DB Destination.
In the OLE DB Destination Editor dialog, ensure that localhost.AdventureWorksDW2012 is selected in the OLE DB Connection manager box.
In the Name of the table or the view box, enter or select [dbo].[FactCurrencyRate].
Select the New button to create a new table. Change the name of the table in the script from Sample OLE DB Destination to NewFactCurrencyRate. Select OK.
Upon selecting OK, the dialog closes and the Name of the table or the view automatically changes to NewFactCurrencyRate.
Verify that the AverageRate, CurrencyKey, EndOfDayRate, and DateKey input columns are mapped correctly to the destination columns. If same-named columns are mapped, the mapping is correct.
Right-click the Sample OLE DB Destination destination and select Properties.
In the Properties window, verify that the LocaleID property is set to English (United States) and the DefaultCodePage property is set to 1252.