Azure数据工厂-区域依赖性 [英] Azure Data factory - Region dependency

问题描述

尊敬的专家，

我们计划将所有资源都放在美国中部Azure地区.但是，Azure数据工厂目前在美国中部不可用.因此，我们在美国东部有一个ADF实例，并正在使用它来促进 中部地区的资源. (例如，在中心区域内，在Azure blob存储到Azure SQL DW之间).

We are planning to have all the resources located in Azure Central US region. However, Azure Data Factory at this point is not available in Central US. Hence, we have an instance of ADF in East US and are using that to facilitate copy activities between resources within central region. (For example between Azure blob storage to Azure SQL DW both within central region).

如果ADF驻留在一个区域中，但是数据移动必须发生在另一个区域内，请问是否存在瓶颈?我确实读过某个地方，只要资源位于同一位置，ADF就是另一个区域就不会 会导致性能问题，并且不算跨地区迁移.任何文档或提示回答此问题的线索都可能真正有帮助.

Could you please let me know if there is any kind of bottle neck if ADF resides in one region but the data movement has to happen 'within' another region ? I did read somewhere that as long as the resources are co-located, ADF being another region doesn't cause performance issues and doesn't count as moving across regions.  Any documentation or clue to answering this question might really help.

非常感谢这里的任何指导.谢谢.

Any guidance here is greatly appreciated. Thank you.

推荐答案

您可以将位于美国中部的公共集成运行时用于2个链接服务(Azure Blob存储和Azure SQL DW)，在创建链接服务时不要使用AutoResolve集成运行时，而是使用Region创建公共IR 在美国中部.

you could use an public Integration Runtime which located in Central US for the 2 linked services (Azure Blob Storage and Azure SQL DW), that it, do not use AutoResolve Integration Runtime when linked service creation instead created a public IR with Region in Central US.

顺便说一句，我们有更多的区域支持数据移动，而不是ADF区域，美国中部是数据移动支持的区域，而不是ADF区域，这就是我在想的意思，这不会引起性能问题?您可以将我们指向该文档. 谢谢.

BTW, we have more regions supported for data movement instead of ADF regions, Central US is a data movement supported region while not an ADF region, that's what I'm thinking you mean doesn't cause performance issues? You could point us to the document. Thanks.

这篇关于Azure数据工厂-区域依赖性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！