Microsoft SQL Server 2008 Integration Services: Problem, Design, Solution

I've worked with SQL Server (97 2000 2005 2008) for 13 years. Was laid off six months ago so I have some time on my hands while I look for work, so I thought I should work on expanding my SQL skills. I have T-SQL down, no problems there.I can do anything needed in SSIS (control flow and data flow), but this book made me realize a major shortcoming in my general approach and the approach of the company I worked at. We treated each SSIS implementation as a separate, unique project. Each SSIS package had it's own configuration setup, non-shared logging and auditing schemes and none of it was scalable. This resulted in a mish-mash of styles in our hundreds of SSIS packages throughout the company.If you have any experience with SQL Server and SSIS, this book can be used as a great roadmap for creating an overall architecture for SSIS implementations. The best time to impose this roadmap is prior to creating any SSIS packages, there are advisories to this effect in the book. Due to my prior experience above, I can tell you they are exactly right in saying that. If you already have a few SSIS packages built, (what's a few? <20?), it wouldn't be a huge effort to go back and retrofit the existing packages into the recommended architecture.I've been angling for a consulting job that requires SQL Server and more importantly, SSIS experience. The customer is changing over from an ETL layer that is T-SQL code-heavy to one that is going to be SSIS-heavy. When I interview, the concepts in this book are going to get me that job.

Reading this book reminds me of why I tend to stay away from Wrox books. Reading a wrox programming book is a little bit like if I wrote to you like this:Example A: Setting up a scripting For Each Loop. To do this just go _____ _______ _______ ______ ______ once you are done just take this and go ______ _______ ______.Now you have it!Have what?....This book is meant primarily for people who ALREADY have experience with SSIS and is NOT MEANT FOR PEOPLE to learn SSIS. Most of my questions dealt with how does this work, how does that work? Wrox is notorious for jumping around and NOT being precise, then of course if you don't follow a hidden part they did not mention you are out of luck. With something as simple as a scripting task with a ForEach loop in Chapter 4 they don't tell you how the User Variable they set up works, then they mention you can script it but it fails with the code they gave because there are variables for the variable that need to be examined. Then you have to download their code to see what they left out in explanation.This is not my first bad experience with a Wrox book, but after this one I know it's deterministic. They may be for very advanced users so I apologize but I don't see the need to leave out steps and this is common with Wrox books of all types. They assume things that are not listed and then you inevitably have to go to their site to download code because that is the only way to find out what they meant they did not list.Very disappointed learning SSIS thus far and will go with a lower rated book as this one is basically for people that already know SSIS and don't need to learn it.

Not a beginner's book. Target audience is medium to expert level professionals.Simply put, should I write code or architect a process flow (package) with minimum code effort to solve business problem? If architecting is a choice then this book is for you.The book covers package framework, design and development. It walks you through design patterns for developing effective SSIS packages. There is a nice section on package's performance with comparison to memory and disk I/O bottlenecks.The book also covers physical infrastructure and deployment by focusing on package deployment on single/multiple computers and talk about processor capacity, RAM and physical disk size.

This book is really good for more advanced users. If you have developed SSIS packages in the past, and want to take the next step to make your systems better, then get this book. I am a developer for a big company and I rarely see advanced "real world" examples of SSIS solutions. I love the first chapter on SSIS logging. Download the code from the website, and it will create your logging tables and procs with just minor modifications to the scripts.I initially put off buying this book for a week because it only had one review at the time (even though it was 5 stars).This is an excellent Book!

So far, I have read only the first 2-3 chapters but I must say that I really found the book very informative. The approaches mentioned are so helpful especially for those who do NOT yet have enough experience with SSIS or IT industry in general.Very well structured and written.

Great book for understanding advanced SSIS patterns. Using this book I was able to come up to speed on complex packages.

THe prose of what I hoped to be a technical manual is really stilted as the authors try and force their commentary into a format of Problem / solution.

Anybody who has done any ETL processing work, either as an IT pro or a business analyst would find this book useful.I still have it around and have recommended it to several friends.

If you are like me and you hate technical books where there are hundreds of pages of useless screenshots and step by step instructions this book is for you.As stated in the title, each section of the book is divided in 3 parts : Problem, Design, Solution. If you are an IT professional it will remind you of : Requirements, Design, Build. I loved the approach.I think this book covers all what you need to know to begin to use SSIS the way it should be used. It is easier to understand if you are already familiar with data warehousing and ETL concepts.

After having been through the previous book, bought this to update to 2008 and found the previous book far easier to follow.The book contains some excellent info, however I found during the hands-on parts, many of the steps that needed to be followed were buried in the main text and were therefore easy to miss.Would (for my tiny brain) prefer numbered steps for these parts.