[4].SSIS Components

So far, you've learned about SSIS objects and process control architecture. Now you will learn about the SSIS components that you use to design, test, deploy, manage, schedule, and execute SSIS packages. Some of the SSIS components reside on the SSIS server, whereas other components reside on your desktop workstation. A sample configuration scenario is shown in Figure 1-2.

Image from book
Figure 1-2: Sample SSIS components configuration scenario

SSIS Development Studio

The Business Intelligence Development Studio (BIDS) is the desktop workstation component you use to design, develop, and test SSIS packages. BIDS provides you with a totally graphical-oriented development environment, allowing you to copy, maintain, and create new packages by using a menu and toolbox drag-and-drop method for development. BIDS is a comprehensive development platform that supports collaboration with source code management and version control; provides debugging tools such as breakpoints, variable watches, and data viewers; and includes the SQL Server Import and Export Wizard to jump-start package development.

Within BIDS, the SQL Server Import and Export Wizard allows you to generate SSIS packages to copy data from one location to another quickly and easily. The Import and Export Wizard guides you through a series of configuration editor pages that allow you to select the source data, select your target destination, and map source to target data elements. You might find this wizard helpful for creating a starting point for a package. Once a package is generated by the wizard, you can then further enhance the package by using BIDS. You will learn how to use BIDS in Chapter 2, "Building Your First Package."

SSIS Runtime Services

SSIS Runtime Services manages storage of packages in .dtsx (SSIS package system file format) files or in the MSDB database and manages and monitors their execution. SSIS Runtime Services saves your package layout, applies configurations, executes packages, manages data source and destination connection strings and security, and supports logging for tracking and debugging. SSIS Runtime Services executables include the package and all its containers, tasks, custom tasks, and event handlers.

After you design, develop, and complete your testing of SSIS packages from your desktop BIDS, you will want to deploy and implement the packages for scheduled or on-demand processing to the SSIS Runtime Services server. In some companies, the deployment of finished packages is oftentimes performed by a production administrator or other authorized group. At other times, packages can be deployed by the developer. Either way, you can use the graphical interface or a command-line utility to configure and complete the package deployment.

SSIS Package Deployment

The SQL Server Management Studio (SSMS) is a desktop workstation component for the deployment and management of packages into production environments. SSMS connects directly to SSIS Runtime Services and provides access to the Execute Package utility, is used to import and export packages to and from available storage modes (MSDB database or SSIS Package Store), and allows you to view and monitor running packages.

There are also two command-line utilities that you can use to manage, deploy, and execute SSIS packages. Use Dtexec.exe to run a package at the command prompt. An alternative to SSMS, Dtutil.exe, provides package management functionality at the command prompt to copy, move, or delete packages or to confirm that a package exists. You will learn all about the roles of these services and other SSIS application deployment procedures later, in Part III of this book, "Managing Packages."

Finally, a more advanced feature is the Integration Services Object Model that includes application programming interfaces (APIs) for customizing run-time and data flow operations and automating package maintenance and execution by loading, modifying, or executing new or existing packages programmatically from within your business applications.

--翻译

到目前为止,您已经了解SSIS对象和过程控制架构。现在,你将了解你使用的设计,测试,部署,管理,调度,执行SSIS包的SSIS组件。一些SSIS组件驻留在SSIS服务器上,而其他组件驻留在您的桌面工作站。图1-2显示了一个示例配置方案。

 
图1-2:样品SSIS组件配置方案
SSIS开发工作室
商业智能开发Studio(BIDS)是你使用的设计,开发的桌面工作站组件,测试SSIS包。 BIDS中提供了一个完全图形化开发环境,让您复制,维护,使用菜单和工具箱拖放式开发方法,并创建新的软件包。 BIDS是一个全面的开发平台,支持源代码管理和版本控制与协作;提供调试工具,如断点,变量手表和数据观众,包括SQL Server导入和导出向导,迅速启动包发展。

在BIDS中,SQL Server导入和导出向导可以让你快速,轻松地从一个位置到另一个数据复制生成的SSIS包。导入和导出向导将引导您通过一系列的配置编辑器的网页,让您选择的数据源,选择您的目的地和地图源到目标的数据元素。您可能会发现这个向导有助于创建一个包的起点。一旦由向导生成一个包,然后你可以通过使用BIDS中进一步加强包。您将学习如何使用在第2章投标,“建立你的第一个包。”

SSIS的运行时
SSIS的运行时服务。dtsx程序(SSIS包系统文件格式)文件,或在MSDB数据库管理软件包的存储和管理,并监督其执行。 SSIS的运行时服务,节省您的封装布局,适用的配置,执行包管理的数据源和目的地的连接字符串和安全,并支持日志记录,跟踪和调试。 SSIS的运行时服务的可执行文件,包括包和所有它的容器,任务,自定义任务和事件处理程序。

在您的设计,开发,并完成您的SSIS包的测试,从您的桌面上的出价,你将要部署和实施进行定期或按需处理的SSIS运行时服务服务器的软件包。常常在一些企业中,部署成品包装生产管理员或其他授权。在其他时间,包可以开发部署。无论哪种方式,你可以使用图形界面或命令行实用程序来配置和完成包部署。

SSIS包部署
SQL Server管理工作室(SSMS)是一个桌面工作站到生产环境的部署和管理包组件。 SSMS中直接连接到SSIS运行时服务,并提供访问执行包实用工具,是用来导入和导出包,并从可用的存储模式(msdb数据库或SSIS包存储区),并允许您查看和监视正在运行的包。

也有两个命令行实用程序,您可以用它来管理,部署和执行SSIS包。使用Dtexec.exe在命令提示符下运行包。 SSMS中,Dtutil.exe,提供软件包管理功能,在命令提示符下,复制,移动或删除软件包或确认包存在。这些服务和其他SSIS应用程序部署程序后,您将了解的角色,在这本书的第三部分,“管理软件包。”

最后,一个更先进的功能是集成服务的对象模型,包括应用程序编程接口的运行时间和数据流量业务定制和自动化装载包维护和执行,修改或执行新的或现有的包,从您的编程(APIS)业务应用程序

原文地址:https://www.cnblogs.com/sanpoye/p/2474794.html