SQL Server provides a single Setup program to install any or all of its components, including Integration Services. Through Setup, you can install Integration Services with or without other SQL Server components on a single computer.
This topic highlights important considerations that you should know before you install Integration Services. Information in this topic will help you evaluate the installation options so that you can make selections that result in a successful installation.
This topic does not include instructions for starting Setup, using the Setup Wizard, or running Setup from the command line. For step-by-step instructions on how to start Setup and select components to install, see Quick-Start Installation of SQL Server 2012. For information about command-line options for installing Integration Services, see Install SQL Server 2012 from the Command Prompt.
Before you install Microsoft SQL Server Integration Services, review the following requirements:
You can install SQL Server Integration Services in the following configurations:
You can install SQL Server Integration Services on a computer that has no previous instances of SQL Server.
You can install SQL Server 2012 Integration Services (SSIS) side-by-side with an existing instance of SQL Server 2005 Integration Services (SSIS) and SQL Server 2008 Integration Services (SSIS).
When you upgrade to SQL Server 2012 Integration Services (SSIS) on a machine that has one of these earlier versions of Integration Services already installed, SQL Server 2012 Integration Services (SSIS) is installed side-by-side with the earlier version.
For more information on upgrading Integration Services, see Upgrade Integration Services. For information about backward compatibility with earlier versions of Integration Services, see Integration Services Backward Compatibility.
After you review the installation requirements for SQL Server and ensure that your computer meets those requirements, you are ready to install Integration Services.
In previous versions of SQL Server, by default when you installed SQL Server all users in the Users group had access to the Integration Services service. When you install SQL Server 2012, users do not have access to the Integration Services service. The service is secure by default. After SQL Server is installed, the SQL Server administrator must run the DCOM Configuration tool (Dcomcnfg.exe) to grant specific users access to SQL Server Integration Services 11.0.
For instructions on how to grant permissions, see Grant Permissions to Integration Services Service.
If you are using the Setup Wizard to install Integration Services, you will use a series of pages to specify components and options. The following table lists only those pages in the Setup Wizard where the options that you select affect your installation of Integration Services:
Select Integration Services to install the Integration Services service and to run packages outside the design environment.
For a complete installation of Integration Services, together with the tools and documentation for developing and managing packages, select both Integration Services and the following Shared Features:
Many data warehousing solutions also require the installation of additional SQL Server components, such as the SQL Server Database Engine, SQL Server Analysis Services, and SQL Server Reporting Services.
Installing on a 64-bit Computer On a 64-bit computer, selecting Integration Services installs only the 64-bit runtime and tools. If you have to run packages in 32-bit mode, you must also select an additional option to install the 32-bit runtime and tools:
Installing on a Dedicated Server for ETL To use a dedicated server for extraction, transformation, and loading (ETL) processes, we recommend that you install a local instance of the SQL Server Database Engine when you install Integration Services. Integration Services typically stores packages in an instance of the Database Engine and relies on SQL Server Agent for scheduling those packages. If the ETL server does not have an instance of the Database Engine, you will have to schedule or run packages from a server that does have an instance of the Database Engine. This means that the packages will not be running on the ETL server, but instead on the server from which they were started. As a result, the resources of the dedicated ETL server are not being used as intended. Furthermore, the resources of other servers may be strained by the running ETL processes
Any selection that you make on the Instance Configuration page does not affect Integration Services or the Integration Services service.
You can only install one instance of the Integration Services service on a computer. You connect to the service by using the computer name.
By default, the Integration Services service is configured to manage packages that are stored in the msdb database in the instance of the Database Engine that is installed at the same time as Integration Services. If an instance of the Database Engine is not installed at the same time as Integration Services, the Integration Services service is configured to manage packages that are stored in the msdb database of the local, default instance of the Database Engine. To manage packages that are stored in a named instance or a remote instance of the Database Engine, or in multiple instances of the Database Engine, you have to modify the configuration file. For more information about how to modify this configuration file, see Configuring the Integration Services Service (SSIS Service).
Review the settings for the Integration Services service on the Service Accounts tab of the Server Configuration page.
If Windows 7 or Windows Server 2008 R2 is installed, the Integration Services service is registered to run under the NT Services\MsDtsServer110 virtual account, and the Startup Type is Automatic. You do not have to enter a password for the virtual account. If Microsoft Vista or Windows Server 2008 is installed, the Integration Services service is registered to run under the built-in Network Service account, and the Startup Type is Automatic. You do not have to enter a password for the built-in Network Service account.
By default, in a new installation, Integration Services is configured not to log events that are related to the running of packages to the Application event log. This setting prevents too many event log entries when you use the Data Collector feature of SQL Server 2012. The events that are not logged are EventID 12288, "Package started," and EventID 12289, "Package finished successfully." To log these events to the Application event log, open the registry for editing. Then, in the registry, locate the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\110\SSIS node, and change the DWORD value of the LogPackageExecutionToEventLog setting from 0 to 1.
Integration Services installs the Integration Services service.
The Integration Services service is installed when you select the Integration Services option on the Feature Selection page. When you accept the default settings on the Server Configuration page, the Integration Services service is enabled and its Startup Type is Automatic.
You can only install a single instance of the Integration Services service on a computer. The service is not specific to a particular instance of the Database Engine. You connect to the service by using the name of the computer on which the service is running.
Integration Services Features Installed on 64-bit Computers
Setup installs various Integration Services features based on the setup options that you select:
When you install SQL Server and select Integration Services for installation, Setup installs all available 64-bit Integration Services features and tools.
If you require Integration Services design-time features, you must also install SQL Server Data Tools (SSDT).
If you require 32-bit versions of the Integration Services runtime and tools to run certain packages in 32-bit mode, you must also install SQL Server Data Tools (SSDT).
64-bit features are installed under the Program Files directory, and 32-bit features are installed separately under the Program Files (x86) directory. (This behavior is not specific to Integration Services or to SQL Server.)
SQL Server Data Tools (SSDT), the 32-bit development environment for Integration Services packages, is not supported on the Itanium 64-bit operating system and is not installed on Itanium servers.