Precautions for installing IntegrationServices in SQLServer

SQLServer provides a single installer to install any or all of its components, including IntegrationServices. Through the installer, you can install IntegrationServices and SQLServer components on a single computer, or install them separately. This topic focuses on understanding how to install IntegrationServices

SQL Server provides a single installer to install any or all of its components, including Integration Services. Through the installer, you can install Integration Services and SQL Server components on a single computer, or separately. This topic focuses on understanding how to install Integration Services

SQL Server provides a single installer to install any or all of its components, including Integration Services. Through the installer, you can install Integration Services and SQL Server components on a single computer, or separately.

This topic focuses on important notes that you should know before installing Integration Services. The information in this topic will help you evaluate the installation options so that you can make the appropriate choices for successful installation.

This topic does not include instructions on starting the installer, using the Installation Wizard, or running the installer from the command line. For step-by-step instructions on how to start the installer and how to select the component to be installed, see SQL Server 2008 quick start. For information about the command line options used to install Integration Services, see how to install SQL Server 2008 from a command prompt.

Prepare to install Integration Services

Before installing Microsoft SQL Server Integration Services, check the following requirements:

• Hardware and software requirements for installing SQL Server 2008
• System Configuration checker check parameters
• Precautions for installing SQL Server

Select Integration Services configuration

You can install SQL Server Integration Services as follows:

• You can install SQL Server Integration Services on a computer without an existing SQL Server instance.
• SQL Server 2008 Integration Services can be installed in parallel with SQL Server 2005 Integration Services or SQL Server 2000 Data Transformation Services (DTS) or existing instances of both.

Important:

Data Transformation Services (DTS) is not recommended ). For more information, see Data Transformation Services (DTS ).

• You can upgrade an existing instance of SQL Server 2005 Integration Services to SQL Server 2008 Integration Services. For more information, see considerations when upgrading Integration Services. For information about backward compatibility with earlier versions of Integration Services, see backward compatibility of Integration Services
• You can upgrade an existing instance of SQL Server 2000 Data Transformation Services (DTS) to SQL Server 2008 Integration Services. For more information, see notes when upgrading Data Transformation Services. For information on backward compatibility with DTS, see support for Data Transformation Services (DTS) in SQL Server 2008 ).

Install Integration Services

After viewing the installation requirements of SQL Server and ensuring that the computer meets these requirements, you can install Integration Services.

If you use the Installation Wizard to install Integration Services, you will use a series of pages to specify components and options. The following table lists only the pages on which the options in the Installation Wizard will affect the installation of Integration Services after selection:

Page	Suggestions
Function Selection	Select Integration Services to install the Integration Services service and run packages outside the design environment. To complete the installation of Integration Services and tools and documents for development and management packages, select Integration Services and the following sharing functions ": · Business Intelligence Development Studio to install the tool used to design the package. · Management tools-complete to Install SQL Server Management Studio for the Management package. · "SQL Server books online" to install documents. · Client tool SDK to install the hosted assembly for Integration Services programming. · Client tool backward compatibility, so that you can install and execute the data transmission 2000 Package task when you need to support the data transmission package. Many Data Warehouse solutions also require the installation of other SQL Server components, such as the SQL Server engine, SQL Server Analysis Services, and SQL Server Reporting Services. Note: If you select to install some SQL Server components on the "function Selection" page of the Installation Wizard, some subsets of the Integration Services components will be installed. These components are useful for specific tasks, but the functions of Integration Services are limited. For example, the "Database Engine service" option will install the Integration Services components required by the SQL Server Import and Export wizard. The Business Intelligence Development Tools (BIDS) option will install the Integration Services components required when designing the package, but the Integration Services service will not be installed and the package cannot be run outside BI Development Studio. To ensure full installation of Integration Services, You must select Integration Services on the "function Selection" page. Install On a 64-bit computer on a 64-bit computer. If Integration Services is selected, only the 64-bit runtime and tool are installed. If you must run the package in 32-Bit mode, you must select other options to install the 32-bit runtime and tool: · If the 64-bit computer runs the x86 operating system, choose Business Intelligence Development Studio or "Administrative Tools-complete ". · If the 64-bit computer runs the Itanium operating system, select "Administrative Tools-complete ". Dedicated for ETL installation to extract, transform, and load (ETL) processes, we recommend that you install a local instance of the SQL Server database engine when installing Integration Services. Integration Services usually stores packages in Database Engine instances and uses the SQL Server Agent to schedule these packages. If the ETL server does not have a database engine instance, you must use the server plan or running package with the database engine instance. This indicates that these packages will not run on the ETL server, but will run on the server where they are started. Therefore, the resources of the dedicated ETL server are not used as expected. In addition, the resources of other servers may be affected by the running of the ETL process.
Instance Configuration	Any selection made on the "instance configuration" page will not affect the Integration Services or Integration Services service. Only one Integration Services service instance can be installed on one computer. You can use a computer name to connect to the service. By default, the Integration Services Service is configured to manage the packages in the msdb database of the Database Engine instance that is installed with Integration Services. If the database engine instance and Integration Services are not installed at the same time, the Integration Services Service is configured to manage the packages stored in the msdb database of the local default database engine instance. To manage packages stored in a naming or remote instance of the database engine or in multiple instances of the database engine, you must modify the configuration file. For more information about how to modify the configuration file, see configure the Integration Services service.
Server Configuration	On the "server configuration" Page, view the settings of the Integration Services service on the "service account" tab. By default, the Integration Services Service is registered to run under the built-in Network Service account, and the "Startup Type" is "automatic ". You do not need to enter the password of the built-in Network Service account.

By default, in a completely new installation, Integration Services is configured to not record running package-related events to Application Event Logs. This setting prevents too many Event Log entries from being generated when you use the data collector feature of SQL Server 2008. Unrecorded events include EventID 12288 "package started" and EventID 12289 "package completed successfully ". To record these events to the Application Event Log, open the registry for editing. In the registry, Locate the HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft SQL Server \ 100 \ SSIS node and change the DWORD value set for LogPackageExecutionToEventLog from 0 to 1.