I have a Virtual Machine in Azure with SQL Server and looking to pull nightly data from on-premises SQL Server via SSIS in the SQL Azure Virtual Machine. I read that VNET needs to be setup for the Azure VM SSIS to access on-prem SQL Server data. Is that correct? If so, what is needed to set it up?
我在Azure中使用SQL Server的虚拟机，并希望通过SQL Azure虚拟机中的SSIS从本地SQL Server中提取夜间数据。我读到需要为Azure VM SSIS设置VNET才能访问本地SQL Server数据。那是对的吗？如果是这样，需要设置什么？
I understand Azure ExpressRoute is another option but since we don't have a huge volume of data to transfer every night, we believe it might not be ideal considering the high cost associated with it.
我知道Azure ExpressRoute是另一种选择，但由于我们每晚都没有大量的数据传输，我们认为考虑到与之相关的高成本，它可能并不理想。
1 个解决方案
#1
4
Yes, VPN needs to be set up between Azure and your on-premises to let them 'see' each other. There are two types of VPN in Azure:
是的，需要在Azure和内部部署之间设置VPN，让他们“看到”彼此。 Azure中有两种类型的VPN：
- Point-to-site (P2S): this type of VPN gateway connection is often used when you want to create a VPN connection from clients to your Azure VNET where your virtual machine resides in. P2S supports IKEv2 or SSTP
- 点对点（P2S）：当您要创建从客户端到虚拟机所在的Azure VNET的VPN连接时，通常会使用这种类型的VPN网关连接.P2S支持IKEv2或SSTP
- Site-to-site (S2S): this type is more for enterprise or complex network infrastructure, also when security needs to be more controlled. Unlike P2S which uses VPN client to connect to Azure VNET, S2S requires VPN device located in your on-premises and this device needs at least one public IP address.
- 站点到站点（S2S）：此类型更适用于企业或复杂的网络基础架构，当需要更加严格地控制安全性时。与使用VPN客户端连接到Azure VNET的P2S不同，S2S需要位于本地的VPN设备，并且此设备至少需要一个公共IP地址。
More about Azure VPN gateway specification: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways
有关Azure VPN网关规范的更多信息：https：//docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways
The decision consideration depends on your data ingestion requirement. If data is not big and the velocity doesn't need to be high, then P2S is quite enough. Moreover, if your on-premises does not already have VPN device plus financial budget and IT resources are limited, you should go with P2S. With P2S, you don't need a VPN device, you just need to create a new VPN gateway in Azure VNET, then set up VPN client (just a free software) including a certificate. The steps of P2S setup is straightforward. This article gives you quick overview of each VPN type and supportability https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-plan-design
决策考虑因素取决于您的数据提取要求。如果数据不大且速度不需要很高，那么P2S就足够了。此外，如果您的内部部署尚未拥有VPN设备和财务预算且IT资源有限，则应使用P2S。使用P2S，您不需要VPN设备，只需在Azure VNET中创建新的VPN网关，然后设置包含证书的VPN客户端（只是一个免费软件）。 P2S设置的步骤很简单。本文为您提供每种VPN类型和可支持性的快速概述https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-plan-design
ExpressRoute is also an option if you really need to establish a private and direct connection between you and Azure datacenter which gives you fastest way to transfer data without going over Internet. Moreover, ExpressRoute is not available all countries.
如果您确实需要在Azure和Azure数据中心之间建立专用和直接连接，ExpressRoute也是一个选项，它为您提供了最快的方式来传输数据而无需通过Internet。此外，并非所有国家/地区都提供ExpressRoute。
Last but not least, you could have a look at Azure Data Factory if you like, including Data Management Gateway. If this is the case, chances are you need to think about a new approach to replace Azure VM SQL Server by PaaS
最后但同样重要的是，如果您愿意，可以查看Azure Data Factory，包括Data Management Gateway。如果是这种情况，您可能需要考虑通过PaaS替换Azure VM SQL Server的新方法
#1
4
Yes, VPN needs to be set up between Azure and your on-premises to let them 'see' each other. There are two types of VPN in Azure:
是的，需要在Azure和内部部署之间设置VPN，让他们“看到”彼此。 Azure中有两种类型的VPN：
- Point-to-site (P2S): this type of VPN gateway connection is often used when you want to create a VPN connection from clients to your Azure VNET where your virtual machine resides in. P2S supports IKEv2 or SSTP
- 点对点（P2S）：当您要创建从客户端到虚拟机所在的Azure VNET的VPN连接时，通常会使用这种类型的VPN网关连接.P2S支持IKEv2或SSTP
- Site-to-site (S2S): this type is more for enterprise or complex network infrastructure, also when security needs to be more controlled. Unlike P2S which uses VPN client to connect to Azure VNET, S2S requires VPN device located in your on-premises and this device needs at least one public IP address.
- 站点到站点（S2S）：此类型更适用于企业或复杂的网络基础架构，当需要更加严格地控制安全性时。与使用VPN客户端连接到Azure VNET的P2S不同，S2S需要位于本地的VPN设备，并且此设备至少需要一个公共IP地址。
More about Azure VPN gateway specification: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways
有关Azure VPN网关规范的更多信息：https：//docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpngateways
The decision consideration depends on your data ingestion requirement. If data is not big and the velocity doesn't need to be high, then P2S is quite enough. Moreover, if your on-premises does not already have VPN device plus financial budget and IT resources are limited, you should go with P2S. With P2S, you don't need a VPN device, you just need to create a new VPN gateway in Azure VNET, then set up VPN client (just a free software) including a certificate. The steps of P2S setup is straightforward. This article gives you quick overview of each VPN type and supportability https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-plan-design
决策考虑因素取决于您的数据提取要求。如果数据不大且速度不需要很高，那么P2S就足够了。此外，如果您的内部部署尚未拥有VPN设备和财务预算且IT资源有限，则应使用P2S。使用P2S，您不需要VPN设备，只需在Azure VNET中创建新的VPN网关，然后设置包含证书的VPN客户端（只是一个免费软件）。 P2S设置的步骤很简单。本文为您提供每种VPN类型和可支持性的快速概述https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-plan-design
ExpressRoute is also an option if you really need to establish a private and direct connection between you and Azure datacenter which gives you fastest way to transfer data without going over Internet. Moreover, ExpressRoute is not available all countries.
如果您确实需要在Azure和Azure数据中心之间建立专用和直接连接，ExpressRoute也是一个选项，它为您提供了最快的方式来传输数据而无需通过Internet。此外，并非所有国家/地区都提供ExpressRoute。
Last but not least, you could have a look at Azure Data Factory if you like, including Data Management Gateway. If this is the case, chances are you need to think about a new approach to replace Azure VM SQL Server by PaaS
最后但同样重要的是，如果您愿意，可以查看Azure Data Factory，包括Data Management Gateway。如果是这种情况，您可能需要考虑通过PaaS替换Azure VM SQL Server的新方法