Hướng dẫn cài import export 32 bit năm 2024
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Show Install Integration Services (SSIS)
In this articleApplies to: SSIS Integration Runtime in Azure Data Factory SQL Server provides a single setup program to install any or all of its components, including Integration Services. Use SQL Server setup to install Integration Services with or without other SQL Server components on a single computer. This article highlights important considerations that you should know before you install Integration Services. Information in this article helps you evaluate your installation options so that your selection results in a successful installation. Get ready to install Integration ServicesBefore you install Microsoft SQL Server Integration Services, review the following information:
Install standalone or side by sideYou can install SQL Server Integration Services in the following configurations:
When you upgrade to the latest version of Integration Services on a computer that has an earlier version of Integration Services, the current version is installed side by side with the earlier version. For more information about upgrading Integration Services, see Upgrade Integration Services. Install Integration ServicesAfter you review the installation requirements for SQL Server and ensure that your computer meets those requirements, you're ready to install Integration Services.
Note Some SQL Server components that you can select for installation on the Feature Selection page of the Setup Wizard install a partial subset of Integration Services components. These components are useful for specific tasks, but the functionality of Integration Services is limited. For example, the Database Engine Services option installs the Integration Services components required for the SQL Server Import and Export Wizard. To ensure a complete installation of Integration Services, you must select Integration Services on the Feature Selection page. Install a dedicated server for ETL processesTo use a dedicated server for extraction, transformation, and loading (ETL) processes, 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 doesn't have an instance of the Database Engine, you have to schedule or run packages from a server that does have an instance of the Database Engine. As a result, the packages aren't running on the ETL server, but instead on the server from which they're started. As a result, the resources of the dedicated ETL server aren't being used as intended. Furthermore, the resources of other servers may be strained by the running ETL processes Configure SSIS event loggingBy 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. The events that aren't 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\130\SSIS node, and change the DWORD value of the LogPackageExecutionToEventLog setting from Install additional componentsFor a complete installation of Integration Services, select the components that you need from the following list:
Next stepsFor more information about Integration Services installation and feature updates, see the following articles: |