EXERCISE TOPIC▼
SSIS EXERCISES▼
SSIS INTEGRATION SERVICES EXERCISES▼
- Data flow tasks (4)
- Basic data transforms (1)
- Data conversion transforms (2)
- Conditional split transforms (5)
- Lookup transforms (4)
- Looping over files (3)
- Looping over rows (2)
- Merge joins (1)
- Previous versions (18)
- Script tasks (1)
- Variables in script (1)
- Script components (2)
- Accessing file attributes (2)
SSIS Integration Services | Looping over files exercise | Loop over Excel workbooks, combining playlists into a table
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.
You can learn how to do this exercise if you attend one of more of the courses listed below!
| Software ==> | SSIS Integration Services (46 exercises) |
| Version ==> | SSIS 2012 and later |
| Topic ==> | Looping over files (3 exercises) |
| Level ==> | Average difficulty |
| Classroom ==> | Introduction to SSIS / Fast track SSIS |
| Online ==> | Introduction to SSIS / Fast track SSIS |
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.
In Management Studio, open the SQL script in the above folder and execute it to generate an empty table:
Your package should fill this table!
The idea is to combine data from the three workbooks in this folder into a single table:
The table you should aim to populate in SQL Server.
Create a package called Something for everyone which looks like this:
To start with, just get the data flow task to import the Elderly.xlsx data into your Playlist table (we'll worry about changing this file in a moment).
When you run this package, you should get a bit of repetition:
You can have too much Englebert ...
Now change the properties of your Excel connection manager so that the connection is an expression whose value changes each time round the loop:
Much better! Well, at least the SSIS package is.
How much energy do you still have left? You could always add a derived column transform within the data flow task to generate the target market column value. Here's a suggestion for the (horrible) expression you could use:
FINDSTRING(REVERSE(@[User::FilePath]),
"\\",1) - 1),".xlsx","")
And now it's definitely time to close the package down!