SSIS Integration Services | Previous versions exercise | A Script Task to count X Factor series and advise Simon

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).

Software ==> SSIS Integration Services  (40 exercises)
Version ==> SSIS 2012 and later
Topic ==> Previous versions  (18 exercises)
Level ==> Relatively easy
Before you can do this exercise, you'll need to download and unzip this file (if you have any problems doing this, click here for help).

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 package called Simon Says, which will count how many series have been made so far and then offer suitable advice to Simon Cowell on whether to make another.  Within this new package, create a couple of variables:

Variables window

We've tentatively set the maximum permissible number of series to 10. Some may think one was too many ...

 

Create a data flow task, and set the source to be the Series worksheet in the workbook in the folder above:

Previewing series

What you should see when you preview the results in the Excel source.

 

Now add a Row Count transform on so that the data flow task looks like this:

Row count transform

Store the number of rows in your NumberSeriesMade variable.

 

Create 3 script tasks as follows to control what happens next:

Script tasks

The first task should end in success or failure, depending on whether we've exceeded the maximum number of permissible series yet.  The other two tasks should display suitable messages in either case.

 

Try running the package with the MaximumNumber variable set to 10 and then 7 (say).  You should see messages something like this:

Success message Failure message
The first message The second message

Again, note that this is NOT the quickest way to solve this problem!

Close your package down.

This page has 0 threads Add post