独立计算机上的 Azure 自托管集成运行时
Azure self-hosted integration runtime on a standalone machine
我们有一个本地 MS-SQL 服务器，所有数据都存储在该服务器上，这也是应用程序的后端。从这个本地服务器，我们想使用数据工厂服务将数据复制到 Azure Data Lake。这需要在应用程序后端服务器上安装 Azure 自托管集成运行时。
是否有任何其他方法，例如，为 IR 安装创建独立服务器并使用此 IR 将数据从应用程序后端复制 activity 到 Data Lake？
我看不出这有什么问题，您不必将它安装在同一台服务器上。第 3 点谈到了这一点：
The self-hosted integration runtime doesn't need to be on the same
machine as the data source. However, having the self-hosted
integration runtime close to the data source reduces the time for the
self-hosted integration runtime to connect to the data source. We
recommend that you install the self-hosted integration runtime on a
machine that differs from the one that hosts the on-premises data
source. When the self-hosted integration runtime and data source are
on different machines, the self-hosted integration runtime doesn't
compete with the data source for resources.
在本地计算机上安装 IR，然后使用启动配置管理器对其进行配置。不需要与数据源位于同一台计算机上。详情可见here.
我们有一个本地 MS-SQL 服务器，所有数据都存储在该服务器上，这也是应用程序的后端。从这个本地服务器，我们想使用数据工厂服务将数据复制到 Azure Data Lake。这需要在应用程序后端服务器上安装 Azure 自托管集成运行时。
是否有任何其他方法，例如，为 IR 安装创建独立服务器并使用此 IR 将数据从应用程序后端复制 activity 到 Data Lake？
我看不出这有什么问题，您不必将它安装在同一台服务器上。第 3 点谈到了这一点：
The self-hosted integration runtime doesn't need to be on the same machine as the data source. However, having the self-hosted integration runtime close to the data source reduces the time for the self-hosted integration runtime to connect to the data source. We recommend that you install the self-hosted integration runtime on a machine that differs from the one that hosts the on-premises data source. When the self-hosted integration runtime and data source are on different machines, the self-hosted integration runtime doesn't compete with the data source for resources.
在本地计算机上安装 IR，然后使用启动配置管理器对其进行配置。不需要与数据源位于同一台计算机上。详情可见here.