This article is the 2nd part of the series of article on SSIS packaging and transformations.

Introduction:

In this article we will see how data can be transferred from SQL Server DB to Excel sheet.

Steps to achieve transforming data from SQL DB to Excel:

Step 1 and Step 2 – Refer to my previous article on the steps at the below url.

Step 3: Since our task is to transform the data from SQL Server DB to Excel sheet , add a Data Flow task in the control task tab of package.dtsx as shown in the below screen and double click on the task which will redirect to the Data Flow tab

[more]

Step 4: In Data Flow tab add an OLE DB Source task and configure it to the database where we need to perform the transformations and select the table as shown in the below screen. In order to follow the steps on how to configure the SQL DB configuration check my previous article as stated above.

Step 5: Now add the destination source (Excel Data source) as shown in the below screen and make the configuration. To do the configuration first drag the green arrow from SQL data source to the Excel destination tasks and then double click on the excel destination task it will open the below screen for configuration

Step 6: Do the mapping of the columns from both the source and the destination tasks as shown in the below screen

Step 7: Once everything is configured (Source and destination) Press F5 to execute the task and you can find the result at the path where we specified the excel sheet. Check the download section to see the excel sheet which is created with this project.

Conclusion

In this article we have seen how to transform the data from DB to Excel sheet:

About Author:
Karthikeyan Anbarasan, Microsoft MVP (Most Valuable Professional) in ASP.NET/IIS Architecture. He is the Founder and Chief Editor of the www.f5debug.net website and has authored books on Windows Phone and Business Intelligence(SSIS). He is also a Passionate Speaker and a Blogger on Microsoft Technologies.

Site Counter

Awards

Disclaimer

This is a personal weblog. The opinions expressed here represent my own and not those of my employer. For accuracy and official reference refer to MSDN/ TechNet. I have documented my personal experience on this blog.