克服Windows Azure Sql数据库150 gb大小限制 [英] Overcoming Windows Azure Sql Database 150 gb size limitation
问题描述
SQL Azure数据库大小限制为150 gb。我已经阅读了他们的文档几次，也搜索在线，但我不清楚这一点：使用联合允许开发人员超过150 gb数据库增长？例如，我可以有几个150GB的联合成员。
如果不是，我如何在Windows Azure上处理大于150 gb的数据库？
基本上，如何在Windows Azure上扩展到超过150 gb
如果没有其他方式是RDS一个好的替代方案（共享任何其他替代方案）
目前不可能有单个数据库大于150G。
唯一的方法是将数据拆分为多个数据库，一个帐户最多可以有149个用户数据库和主数据库，或者使用SQL Azure Federations。目前，如果我没有错误，支持的联合会总数是 Int16.MaxValue - 1 。每个联盟实际上是一个独立的数据库，对开发人员来说是透明的，可以高达150GB。
然而，SQL Azure Federations有自己的优点和缺点，数据访问层重构。如果您有兴趣，可以在SQL Azure联合会上查看这些精彩视频：
UPDATE
我不会完全同意@ryancrawcour。他解释的只是位于水下的冰山的峰顶。所需的重新分解的数量实际上取决于数据如何从应用程序中消耗。我只是提到几个因素的考虑（这不是完整的图片）。请考虑以下任意情况：
- 所有联盟常见的数据（如何获取此数据）
- 存储proc，即后处理数据 - 您必须在每个和曾经的联合成员中进行迭代，并执行该存储过程。没有办法执行Stored proc一次，并在所有联合会中处理数据。
- 汇总分布在多个联盟成员之间的数据
- 列出来自多个联合成员的数据。
这些只是几个操作，您需要考虑，在每个查询之前需要仅更改连接字符串并执行一个使用联合...。实际上使用SQL Azure Federations你根本不需要更改连接字符串。它是所有相同的SQL Azure连接字符串。 USE FEDERATION ...语句是在每个查询之前执行的语句。但它的方式不只是唯一的事情。如果一个人使用EntityFramework（模型第一，或代码第一，或任何）。事情变得更加复杂，需要真正了解SQL Azure联合会。
我会说SQL Azure联合会是不同的思考数据，建模和规范化的方式。 / p>
UPDATE 2 - Microsoft公布的新数据库大小
2014年，单个数据库的最大大小已增加到500GB。迄今唯一可用的资讯在这里。请注意，管理门户仍然不显示此选项（截至今天和现在：4. Apri 2014，15:00 GMT + 0：00）。
SQL Azure has a database size limit of 150 gb. I have read through their documentation several times and also searched online but I'm unclear about this: Does using federations allow a developer to grow beyond a 150 gb data base? For example can I have several 150GB federation members.
If not, how can I handle a database larger than 150 gb on Windows Azure?
basically, How do I scale out beyond 150 gb on Windows Azure
If theres no other way is RDS a good alternative(share any other alternatives)
Currently it is not possible to have a single database larger than 150G.
The only approach is to either split the data into multiple databases, one account can have up to 149 user databases plus the master DB, or use SQL Azure Federations. Currently, if I am not mistaken, the total number of Federations supported is Int16.MaxValue - 1. Each federation is actually a separate database, transparent to the developer, which can be up to 150GB.
However, SQL Azure Federations has its own pros and cons, along with some data access layer re-factoring. If you are interested you may check out these cool videos on SQL Azure Federations:
UPDATE
I will not completely agree with @ryancrawcour. What he explains is just the peak of the iceberg lying bellow the water. The amount of required re-factoring really depends on how data is consumed from the application. I will just mention a few factors for considerations (which are not complete picture at all). Consider any of the following:
- Data that is common for all federations (how you get this data)
- Stored proc, that post-processes data - you have to iterate in each and ever federation member and execute that stored proc. There is no way to execute the Stored proc once and process data in all the federations.
- Aggregate data, which is spread across more than 1 federation member
- List data from more than one federation member.
These are just few operations that you will need to consider, and that does not require "just change in connection string and execute one use federation ..." before each query. Actually using SQL Azure Federations you don't need to change the connection string at all. It is all the same SQL Azure connection string. The "USE FEDERATION ..." statement is what you have execute before each query. But it is way not just the only thing. And how about if one is using EntityFramework (model first, or code first, or whatever). Things get even more complicated and need real understanding of SQL Azure Federations.
I would say that SQL Azure Federations is different way of thinking about data, about modelling and normalizing.
UPDATE 2 - new Database sizes announced by Microsoft
As of 03. April 2014 the maximum size for a single Database has been increased to 500GB. The only available information to date is here. Be aware that the management portal still doesn't show this option (as of Today and now: 4. Apri 2014, 15:00 GMT+0:00).
这篇关于克服Windows Azure Sql数据库150 gb大小限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
