考虑到Datawarehouse的AZURE

本文介绍了考虑到Datawarehouse的AZURE的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述 29岁程序员，3月因学历无情被辞！ Hi Experts， 我们正在考虑使用Microsoft Azure来托管数据仓库解决方案。 Q1。在典型的实现中，如果我们有一个托管的OS磁盘，它就会提到存储事务。这代表了什么？当我们查看定价页面时，默认情况下它会讨论100,000个交易单位，它会在小文本中显示10,000个交易。总共100,000 * 10,000笔交易是什么？&bbsp; b 。如果我们使用SQL数据仓库，它会在DWU中显示配置。在标准小于50GB的数据仓库中你认为100 DWU会足够好吗？是否有可以使用的基准和参考？Hi Experts,We are considering Microsoft Azure to host a data-warehousing solution.Q1. In a typical implementation, if we are having a managed OS Disk it has storage transactions mentioned. What does this represent. When we look into the pricing page, by default it talks about 100,000 transaction units and it says 10,000 transactions in small text. So is it 100,000 * 10,000 transactions in total? Q2. If we go with SQL Data warehouse it shows the configuration in DWU. On a standard less then 50GB size of data warehouse do you think 100 DWU will be good enough? Are there any benchmarks and references that can be used? Q3。如何计算数据上传和下载？如果我们超过限制，我们会自动转移到下一层吗？例如，从100 DWU到200 DWU。Q3. How data upload and download is getting calculated? And if we exceed the limit will we be moving to the next tier automatically? say from 100 DWU to 200 DWU for example. Q4。如果我们在同一个Microsoft Azure域中托管了2个VM，一个用于应用程序，一个用于数据库，那么在计算使用情况时，这些VM之间是否会单独计算读取和写入？ Q4. If we have 2 VMs hosted within the same Microsoft Azure domain, one for application and one for Database, will the reads and writes will be counted individually between these VMs when it comes to calculating the Usage?  等待您的专家意见。Awaiting your expert opinions.我们需要注意的其他事情是什么？Any other things that we need to watch out for?谢谢 Rajesh推荐答案您是否从当前部署在on的SQL Server实例迁移 - 优秀的环境？如果是，那么调整解决方案的最有效方法是使用数据仓库大小调整计算器：  Azure SQL数据仓库DWU计算器Are you migrating from an SQL Server instance currently deployed in an on-premise environment? If you are, the most efficient means for sizing a solution is to use the Data Warehouse Sizing Calculator: Azure SQL Data Warehouse DWU Calculator此Stack Overflow线程：  如何计算Azure SQL数据仓库DWU？是一个很棒的解释它是如何扩展的。This Stack Overflow thread: How to calculate Azure SQL Data Warehouse DWU? is a great in explaining how it scales.因此，对于Q2，我无法确切地说出最合适的定价等级，但如果你从200 DWU开始并且在峰值需求，您可以扩展资源并在没有时缩小。 So, for Q2, I can't really say exactly what pricing tier is best but if you start with 200 DWU and that is insufficient during peak demand, you can scale up resources and scale down when not. 关于Q1，您引用的存储数据不适用于Azure SQL数据仓库存储定价。  ;With regard to Q1, the storage figures you are quoting do not apply to Azure SQL Data Warehouse storage pricing.  数据存储和sn apshots 数据存储按照Data storage is charged at the rate of 注意 - 存储交易不计费。您只需为存储的数据而非存储事务付费。Note—Storage transactions are not billed. You only pay for stored data and not storage transactions.您说的是当Azure SQL数据仓库PaaS服务未部署为IaaS服务时正在部署的虚拟机。因此，到第四季度答案是否定的，但不适用。  我希望这会有所帮助。You speak of VMs being deployed when the Azure SQL Data Warehouse PaaS service is not deployed as an IaaS service. So, to Q4 the answer is no and it does not apply. I hope this helps. Mike 这篇关于考虑到Datawarehouse的AZURE的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！ 上岸，阿里云！