ALL SOFTWARE EXERCISES
- EXERCISES HOME PAGE (862)
- Access 2010 (66)
- Access VBA Macros (17)
- Advanced VBA (29)
- ASP.NET MVC (0)
- ASP.NET webforms - C# (25)
- ASP.NET webforms - VB (27)
- Excel 2010 (83)
- Excel 2013 (10)
- Excel 2016 (0)
- Excel VBA Macros (37)
- Power BI - Excel 2013 (25)
- Power BI - Excel 2016 (23)
- Power BI Desktop (26)
- PowerPivot 2010 (26)
- Report Builder 3.0 (42)
- SQL (156)
- SSAS - multidimensional (21)
- SSAS - tabular (29)
- SSIS Integration Services (40)
- SSRS Reporting Services (53)
- Visual Basic 2010 (42)
- Visual C Sharp 2010 (65)
- WPF - Visual C# (20)
SSIS INTEGRATION SERVICES EXERCISES
Exercise: Create a new column within a script component
This exercise is provided to allow potential course delegates to choose the correct Wise Owl Microsoft training course, and may not be reproduced in whole or in part in any format without the prior written consent of Wise Owl.
The answer to the exercise will be included and explained if you attend the relevant Wise Owl course (sadly, only in the UK for now).
You need a minimum screen resolution of about 700 pixels width to see our exercises. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.
Create a new package called Derived columns are better. Within this create a single data flow task as follows:
The task should import rows from the Series worksheet in the Excel workbook in the above folder, then use a script component to set the value of a new column called RunLength to equal the duration of each series in days (see below for code excerpt). Finally, the task should use Union All as a dead-end destination, and display the results in a data viewer on the pipe leading to this.
Here's some sample code to work out the difference between two dates in days, which may help you:
// take the time difference, and convert it into days
Row.RunLength = (Row.Finishdate - Row.Startdate).Days;
When you run your package, you should see this in the data viewer:
The first few series in the data viewer, showing the length of the series in days.
Final thought: why do you suppose that this exercise suggests giving the package the name it does?