LearnNowOnline

Control flow containers provide ways to group tasks so that they execute together. Containers allow you to group control flow tasks for execution, to group tasks for repeated execution given some condition, to repeatedly execute group tasks for each data member in some kind of collection and to easily set properties that affect all its contained tasks. In the looping containers you can control how and whether the member tasks of each execution group interact with each other or to share the same variable scope defined for that container. They also provide a way to define success and failure through precedents constraints for the groups of tasks as a whole. In this course you’ll learn about all containers you can use including the mostly invisible task host container that Integration Services creates for you automatically any time that you add a task to a control flow. We’ll explore all the containers and you’ll see various demos that show how you can take advantage of them. A transaction is a core concept of relational data base systems. It is one of the major mechanisms through which a data base server protects the integrity of data by making sure the data remains internally consistent. SQL Server has always had rich support for transactions and Integration Services hooks into that support. You’ll see how to implement transaction for both a package as well as for smaller units using containers. With smart transaction implementation you can build remarkably robust packages.

This course assumes that you have a basic familiarity with the concept of relational databases and a basic understanding of what SQL Server is and the high-level tools in it, as well as how to create and manage objects using Management Studio. You should also have a basic understanding of how SQL Server implements security, including its authentication and authorization schemes, and how to assign permissions on securable objects to principals. You should know the fundamentals of Transact-SQL to write queries to retrieve data and join data from multiple tables, and how to execute scripts using the query editor in Management Studio. You must also know how to connect to an instance of SQL Server 2012 using the various connection dialog boxes in Management Studio and development tools. It will be very helpful, but not absolutely necessary, to have experience with .NET development using Visual Studio 2012 or later for the portions of the course that deal with SQL Server Data Tools (which is a lot of it). At the very least, we’ll assume that you are well familiar with the Visual Studio user interface. This course assumes no prior knowledge of SQL Server Integration Services.