Đang chuẩn bị liên kết để tải về tài liệu:
Hands-On Microsoft SQL Server 2008 Integration Services part 26

Không đóng trình duyệt đến khi xuất hiện nút TẢI XUỐNG Tải xuống

Hands-On Microsoft SQL Server 2008 Integration Services part 26. Deploy and manage high-performance data transformation solutions across your enterprise using the step-by-step techniques in this fully revised guide. Hands-On Microsoft SQL Server 2008 Integration Services, Second Edition explains the tools and methods necessary to extract conclusive business intelligence from disparate corporate data. Learn how to build and secure packages, load and cleanse data, establish workflow, and optimize performance. Real-world examples, detailed illustrations, and hands-on exercises are included throughout this practical resource. . | 228 Hands-On Microsoft SQL Server 2008 Integration Services For the MSDB database of the remote SQL Server you ll modify the ServerName element as shown ServerName RemoteSQLServerName ServerName And for the File System folder on a remote server you ll modify the StorePath element as shown StorePath RemoteFileServerName ShareName StorePath You will have to restart the SQL Server Integration Services 10.0 service for changes to take effect. After restart when you connect to the local instance of Integration Services using SQL Server Management Studio the MSDB folder in Stored Packages will show the packages saved to the remote SQL Server and the File System folder will show the packages saved to the file share on the remote server. Managing Packages on an Instance of an SQL Server One important point is to understand that Integration Services is not a multi-instance application like SQL Server. However it is aware of SQL Server instances and can connect to them. For example you might prefer to save your packages in the instance of SQL Server to which they relate instead of saving them into default instance. In that case you can modify the ServerName element as follows and connect to the MSDB database of the specified instance of SQL Server. ServerName ServerName InstanceName ServerName You will have to restart the SQL Server Integration Services 10.0 service for changes to take effect. After restart when you connect to Integration Services using SQL Server Management Studio the MSDB folder in Stored Packages will show the packages saved to the specified instance. Connecting to Integration Services on a Remote Server Sometimes you may also want to connect to Integration Services on a remote server for instance you may be using SQL Server Management Studio on your client machine but connecting to remote Integration Services. You can do so when you choose Integration Services in the Server Type field and the remote server name in the Server Name field in the Connect To