Inside Integration Services Tools: Introduction
SQL Server 2005 introduces a new (ETL) component, Integration Services. Integration Services replaces Data Transformation Services (DTS), first introduced in SQL Server 7.0 and enhanced in SQL Server 2000. However, Integration Services is not a new and improved version of DTS; instead, Integration Services is redesigned and rebuilt from the ground up. This means a new and very different object model, an expansive application programming interface (API) for programming the object model, and a plethora of graphical tools and wizards to create the packages that comprise an ETL solution. This includes the SQL Server Import and Export Wizard to quickly build a simple package that extracts and loads data; SSIS Designer to create complex packages with multiple inputs and outputs, in-line business intelligence, and data cleaning capabilities; tools to implement logging, configurations, updatable properties, and variables in packages; and finally, the tools to deploy the ETL solution.
In SQL Server 7.0 and SQL Server 2000, the Microsoft Management Console (MMC) snap-in, Enterprise Manager, hosted the tools for SQL Server components, including DTS. In SQL Server 2005, it's goodbye MMC, and hello to the "studio" environment. SQL Server 2005 introduces two studios: Business Intelligence Development Studio and SQL Server Management Studio. Both environments are similar to Microsoft Visual Studio; they include Solution Explorer and Server Explorer views, a Properties window, and windows for debugging. In addition, many of the tools for Integration Services are tightly integrated with the look and feel of the "studio" environment. For example, the windows germane to Integration Services, such as the ones for work¬ing with variables or viewing log entries, behave just like the windows that are an intrinsic part of the "studio" environment.
When you are using Integration Services, you are working in both Business Intelligence Development Studio and SQL Server Management Studio. If you are a developer that uses graphical tools to develop business ETL solutions, you can create, debug, and maintain packages in the Business Intelligence Development Environment. If you are an administrator, you can manage packages in SQL Server Management Studio. Either way, you will find that the tools provided by Integration Services go a long way toward addressing the tasks that were just plain difficult to do in the earlier Microsoft ETL offerings. This chapter tells you about these tools.
Use the following table of contents to navigate to chapter excerpts, or click here to view Inside Integration Service Tools in its entirety.
Inside SQL Server Integration Services Tools
Part 1: Integration Services overview
Part 2: Integration Services tools overview
Part 3: Using Integration Services tools in business scenarios
Part 4: Common package development scenarios
Part 5: Common package deployment scenarios
Part 6: Common package management scenarios
|About the book|
|Microsoft SQL Server 2005's high-powered management tools can dramatically improve DBA productivity and effectiveness. Now there's a comprehensive guide to SQL Server 2005's toolset, straight from the Microsoft team that created it. This book covers the entire toolset in unprecedented depth, guides database professionals in choosing the right tools, and shows them how to use various tools collectively to solve real-world problems. Purchase Inside SQL Server 2005 Tools from Addison-Wesley.|
|About the author|
|Lead author Michael Raheem is a senior product manager in the SQL Server Marketing team at Microsoft. Michael currently leads SQL Server enterprise marketing efforts, including high availability, scalability, performance, and SQL Server Always On Technologies. Prior to joining the marketing team, he led the design and implementation of several SQL Server 2005 tools such as Management Studio, Upgrade Advisor, Database Mail and Surface Area Configuration. Michael has spoken at several conferences, including TechEd, TechReady, PASS and SQL Connections. Additionally, he has contributed to the Answers from Microsoft column in SQL Server Magazine and has over 13 years of experience in designing and developing solutions with Microsoft SQL Server.|