Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Tim Mitchell

Tim Mitchell is a business intelligence consultant, author, trainer, and SQL Server MVP with over a decade of experience. Tim is the principal of Tyleris Data Solutions and is a Linchpin People teammate. Tim has spoken at international, regional, and local venues including the SQL PASS Summit, SQLBits, SQL Connections, SQL Saturday events, and various user groups and webcasts. He is a board member at the North Texas SQL Server User Group in the Dallas area. Tim is coauthor of the book SSIS Design Patterns, and is a contributing author on MVP Deep Dives 2. You can visit his website and blog at TimMitchell.net or follow him on Twitter at twitter.com/Tim_Mitchell.

Book Review – SQL Server Integration Services: Problem – Design – Solution

525760 cover.indd I usually don't do book reviews (at least publicly, anyway), but when I find a piece of work that I really get a lot out of, I don't mind sharing my experience. Such was the case with a book I finished recently. SQL Server 2008 Integration Services: Problem - Design - Solution is a concise guide to becoming a better ETL developer, written by four highly experienced industry experts. After reading this book, I can recommend it without hesitation!

From the first few pages, it's obvious that this book is different from many other SSIS books. Rather than trying to teach the reader how to use the software, this book instead focuses on common business problems and the methodology behind solving them. The authors assume some familiarity with SSIS, so you won't find a comprehensive how-to manual if you've never created a package before. That being said, the concepts presented here are not so complex that only highly seasoned ETL developers will understand them; to the contrary, the book illustrates a number of simple yet practical approaches, along with relevant examples, that audiences of various skill levels will get something out of it.

One of the most relevant topics covered was the concept of building an SSIS management framework, which was my favorite part of the book. Having recently moved from an environment with a relatively small number of packages to a consulting role where I might interact with hundreds of packages a month, I found that a solid ETL framework is a critical component of success. Chapter 2 of the Problem - Design - Solution book explains why, and illustrates how, one would build an SSIS management framework. For anyone that has struggled with a large number of packages or has wrestled with the shortcomings of the built-in SSIS logging tools, this chapter should prove useful as both a guide and a best practices reference. Further into the book, the authors cover other topics essential to data warehousing ETL, including data cleansing and fact and dimension table ETL. The authors go on to cover scripting in SSIS, one of my favorite topics, and do a good job of addressing scripting patterns in both the script task and script component. Finally, the book reviews ways to monitor and improve SSIS performance.

I consider a technical book to be successful if it contains the right mix of information so that I can immediately apply what I've learned to legitimate problems and situation. To that end, this book is a winner in my opinion; even though I have been developing ETL processes in SSIS for years, I was able to walk away with some practical techniques that I began using almost immediately. Experienced ETL developers, as well as those with only a little SSIS experience, will likely find this book very useful.

Comments

Posted by Steve Jones on 16 April 2010

That's quite a recommendation from someone that I see as a pretty good go-to-guy for SSIS. I might need to check this one out.

Posted by Anonymous on 18 April 2010

Pingback from  Dew Drop – Weekend Edition – April 16-18, 2010 | Alvin Ashcraft's Morning Dew

Posted by Nik on 6 January 2012

This book is grate, it gives you good ideas, one thing  that i achived is , in the book it talks about

1- SSIS management framework

2- Pakage framework

well I came up with something new , "Pakage Master framework" which goes in between the above item

what it does is that it can handle "SSIS management framework" for old packages (ie the one that i had designed in 2004) its kind of dynamic, and the second thing is that it calls the child packages and adds features like error handling and Looping files , and excel sheet and etc... basically i am controlling everything dynamically, to a point that i can have my child packages as smallas possible and the master pkg will handle everything. another thing is that if i have to add a feature to all my packages i just change my master package insted of editing all of my packages.

why did i came up with this idea? well i have

8 customers , each customer has min 4 SQL server , and on each SQL server i have more than 300 packages, and its growing every day, you do the math.

Posted by Nik on 9 January 2012

This book is grate, it gives you good ideas, one thing  that i achived is , in the book it talks about

1- SSIS management framework

2- Pakage framework

well I came up with something new , "Pakage Master framework" which goes in between the above item

what it does is that it can handle "SSIS management framework" for old packages (ie the one that i had designed in 2004) its kind of dynamic, and the second thing is that it calls the child packages and adds features like error handling and Looping files , and excel sheet and etc... basically i am controlling everything dynamically, to a point that i can have my child packages as smallas possible and the master pkg will handle everything. another thing is that if i have to add a feature to all my packages i just change my master package insted of editing all of my packages.

why did i came up with this idea? well i have

8 customers , each customer has min 4 SQL server , and on each SQL server i have more than 300 packages, and its growing every day, you do the math.

Posted by Nik on 10 January 2012

This book is grate, it gives you good ideas, one thing  that i achived is , in the book it talks about

1- SSIS management framework

2- Pakage framework

well I came up with something new , "Pakage Master framework" which goes in between the above item

what it does is that it can handle "SSIS management framework" for old packages (ie the one that i had designed in 2004) its kind of dynamic, and the second thing is that it calls the child packages and adds features like error handling and Looping files , and excel sheet and etc... basically i am controlling everything dynamically, to a point that i can have my child packages as smallas possible and the master pkg will handle everything. another thing is that if i have to add a feature to all my packages i just change my master package insted of editing all of my packages.

why did i came up with this idea? well i have

8 customers , each customer has min 4 SQL server , and on each SQL server i have more than 300 packages, and its growing every day, you do the math.

Leave a Comment

Please register or log in to leave a comment.