克服的Windows Azure SQL数据库150 GB大小的限制 [英] Overcoming Windows Azure Sql Database 150 gb size limitation
问题描述
SQL Azure中有150 GB的数据库大小限制。我通过他们的文件多次阅读，也网上搜索，但我不清楚这一点：是否使用联盟允许开发人员增长超过150 GB的数据基础？例如，我可以有几个150GB联盟成员。
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.
如果不是，我怎么能处理的数据库比在Windows Azure上150 GB的？
If not, how can I handle a database larger than 150 gb on Windows Azure?
基本上，我如何向外扩展超过150 GB在Windows Azure上
basically, How do I scale out beyond 150 gb on Windows Azure
如果世界上没有其他办法RDS是一个不错的选择（共享任何其他的替代品）
If theres no other way is RDS a good alternative(share any other alternatives)
推荐答案
目前是不可能有一个单独的数据库比150G大。
Currently it is not possible to have a single database larger than 150G.
唯一的办法是要么分裂数据分成多个数据库，一个账号最多可以有149用户数据库以及主数据库，或使用SQL Azure的联合会。目前，如果我没有记错，支持联合会的总数 Int16.MaxValue - 1 。每个联合实际上是单独的数据库，透明的显影剂，它可高达150GB
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.
但是，SQL Azure的联盟都有自己的优点和缺点，用一些数据访问层的重构一起。如果你有兴趣可以签出的SQL Azure的联合会这些很酷的视频：
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:
- Building Scalable Apps with SQL Azure
- Using SQL Azure Database Federations
更新
我不完全同意@ryancrawcour。他解释说只是冰山躺在波纹管的水只是高峰。需要重新分解量真的取决于如何将数据从应用程序消耗。我只提了一个考虑因素，一些（这是不完整的画面在所有）。考虑以下任何一项：
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:
- 数据是很常见的所有联合会（你如何得到这个数据）
- 存储过程，即后处理数据 - 你必须在每个迭代和不断联合会会员和执行存储过程。有没有办法在所有的联合会执行存储过程一次和处理数据。
- 汇总数据，这是在超过1联合会会员 取值$ P $垫
- 列表从多个联邦成员的数据。
- 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.
这些都是你需要考虑的只有几操作，每个查询之前，不需要刚刚在连接字符串的变化和执行一个使用联邦...。使用SQL Azure的联盟其实你并不需要在所有更改连接字符串。它是所有相同的SQL Azure的连接字符串。 用联邦...语句是你每次查询之前执行。但它的方式不只是唯一的事情。而怎么样，如果用户正在使用的EntityFramework（型号第一，或code首先，或其他）。事情变得更加复杂，需要SQL Azure的联合会真正的理解。
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.
我要说的是，SQL Azure的联合会是想着数据，约建模和标准化的方式不同。
I would say that SQL Azure Federations is different way of thinking about data, about modelling and normalizing.
更新2 - 微软宣布了新的数据库大小
截至2014年03月的单个数据库的最大大小已增加到500GB。唯一可用的信息日期<一个href=\"http://www.microsofttrends.com/2014/04/03/improvements-to-azure-sqlincreased-size-limit-to-500-gb-and-an-improved-sla-at-99-95/\"相对=nofollow>在这里。请注意，管理门户仍然未显示该选项（如今天和现在：4. 2014年APRI，15:00 GMT + 0：00）。
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屋！
