在云上选择正确的数据库 Azure SQL
我们正在构建一个应用程序，一个广告服务平台，其中包括许多流程，例如报告、存储用户数据、请求、广告商信息、发布商信息等。此外，我们将生成优化文件以提供更好的广告。
我们使用 Azure 来提供云服务。我们希望从 azure 上的 appfabric 及其架构中受益。
我的问题与 Azure SQL 相关。有谁有使用 Azure DB 的经验吗？有哪些优点和缺点？性能、可靠性、挑战？
在选择 Azure DB 时，我们应该对哪些内容进行基准测试或原型设计？
您有什么想法或想法想分享，尤其是与云数据库相关的想法或想法吗？一致性、可用性、部分容忍、复制？
谢谢。
We are building an application, an ad serving platform, which will include many processes such as reporting, storing user data, requests, advertiser info, pubisher info etc. Moreover, we will be generating optimization files to serve better ads.
We are using azure for cloud services. We are hoping to benefit from appfabric on azure and their architecture.
My question is related to Azure SQL. Does anyone have any experience with Azure DB, what are the advantages, disadvantages? Performance, reliability, challenges?
While choosing Azure DB, what are things should we benchmark or prototype?
Any ideas or thought, you would like to share, especially related to database on cloud? COnsistency, availability, Partial Tolerance, replication?
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
SQL Azure 的优点是您可以针对人们拥有丰富经验的相当标准的 SQL 数据库进行开发。使应用程序迁移到 Azure 变得非常容易。
我看到的缺点是：
1. 备份有限。这种情况很快就会好起来，但它可能永远不是许多人想要的那种备份。
2. 某些 SQL Server 功能不可用，但 95% 可用。
3. 无法真正控制数据库服务器硬件。
4. 价格可能是一个问题，具体取决于您的数据库大小。
除此之外，SQL Azure 对我来说效果很好。
Advantage of SQL Azure is that you can develop against a pretty standard SQL database that people have lots of experience with. Make migration of an app to Azure pretty easy.
The disadvantages i have seen are:
1. Limited backup. This is getting better soon, but it may never be the kind of backup many people want.
2. Some SQL Server features not available, but 95% are.
3. No real control over database server hardware.
4. Price might be an issue, depending on your database size.
Other than that, SQL Azure works well for me.
您确实需要调整数据大小。
SQL Azure 非常适合具有关系需求的小型（<1 GB 或几 GB）。它为现有 SQL Server 开发人员提供了轻松的入门方式，并使开发复杂的报告变得非常容易。
然而，一旦数据大小增加超过几 GB，它就开始变得更加昂贵。此外，扩展 SQL Azure 的模式并不像扩展 Windows Azure 数据库那么简单 - 尽管联邦的新功能应该使其更简单，但它仍然与扩展 SQL Server 不同（人们通常会扩展 - 这里在 SQL Azure 中，有 50 GB 的限制，建议的模式是扩展到更多数据库）。
因此，根据您拥有的内容（请求，可能是用户单击数据等），这确实会增加很多，最好将所有这些保存在 Windows Azure 数据库而不是 SQL Azure 中。您还可以采取双重方法，将一些数据保存在 SQL Azure 中以便更容易进行报告，然后将大量数据保存在 Windows Azure 中。
建筑师好！可以省很多事啊！
You really need to size your data.
SQL Azure is perfect for small (<1 GB or few GBs) with relational requirements. It provides easy on-boarding for existing sql server developers and makes it really easy to develop complex reports.
However once the data size increases beyond a few GBs, it starts becoming more expensive. Also the patterns for scaling SQL Azure is not as simple as scaling Windows Azure Database - although the new feature of Federations is supposed to make it simpler, it is still not the same as scaling SQL Server (which people would normally scale-up - here in SQL Azure there is a limit of 50 GB and the recommended pattern is to scale-out to more databases).
So, going by what you have (requests, maybe user click data, etc) which can really increase a lot, it might be better to save all this in Windows Azure database instead of SQL Azure. You can also take a dual approach, by saving some data in SQL Azure so that it is easier to report against, and then have high quantity data saved in Windows Azure.
Architect well! It could save a lot!
我们将其用于网络应用程序。
经验：
我们几乎没有遇到任何挑战，因为它很容易使用，因为它提供与更熟悉的 SQL 服务器相同的 TDS 接口，因此开发人员可以在需要时轻松适应。这为我们节省了大量时间，而这些时间通常是开发人员必须学习新工具所占用的。
总的来说，我发现它具有良好的性能并且相当可靠。
其他想法：
-可管理性
节省大量 IT 相关成本
- 可扩展性
轻松进入新市场
模型
希望这有帮助！
We used this for a web application.
Experience:
We faced hardly any challenges as it was easy to use because it provides the same TDS interface as the more familiar SQL server so developers can easily adapt if need be. This saved us a lot of time that is usually taken up with Developers having to learn new tools.
Overall I found it to be consistent with good performance and quite reliable.
Other thoughts:
-Manageability
saving on a lot of IT related costs
-Scalability
reach new markets easily
model
Hope this helps!
尽管已经回答了这个问题，但我想我还是要添加一些更多信息。
在云中，您有三个存储选项，每个选项都有自己的数据集：
至于性能方面的考虑，blob 存储确实很快。我没想到会这么快。 SQL 也不错，毕竟它是普通的 MS SQL 数据库。由于它位于“靠近”您的实例，因此网络延迟并不比它位于数据中心的单独计算机中大多少。
有关定价的最新信息，请查看此 Windows Azure 平台优惠。定价专家，所以我的数据是粗略估计。
Although this has been answered already, I'd figure I add some more info to it anyway.
In the cloud, you have three storage options, each for its own set of data:
As for performance considerations, the blob storage is really fast. I didn't expect it to be this fast. SQL does good as well, it is after all your normal MS SQL database. Since it's located "close" to your instance, the network latency is not that much bigger than it would be were it located in a separate machine in your data center.
For up to date info on pricing, look at this Windows Azure Platform Offers. I'm not an expert in pricing, so my figures are rough estimates.
您可以在 SQL 上找到有关 SQL DB 产品及其相应吞吐量的更多信息。数据库定价页面。另外，请查看有关新 SQL 的详细信息DB V12提供与SQL Server引擎近乎完全的兼容性。
编辑（4/29）：
查看新的 Elastic DB 产品（预览版）。 定价页面已更新为 Elastic DB 价格信息。
You can find out more about SQL DB offerings and their corresponding throughput on the SQL DB pricing page. Also, do check out details on the new SQL DB V12 that provides nearly complete compatibility with SQL Server engine.
Edit (4/29) :
Check out the new Elastic DB offering (Preview) announced at Build today. The pricing page has been updated with Elastic DB price information.
首先要做的是查看SQL Azure 的功能列表，以确保这满足您的需求（它可能会），然后是开始页面。
然后还有免费实验室：SQL Azure 实验室。
您可以获得 30 天的免费实时 1GB 数据库。
您可能会对 SQL Azure 团队博客感兴趣。
The first thing to do is look at SQL Azure's feature list to ensure this meets your needs (it probably will), and then the get started page.
Then there are free Labs: SQL Azure Labs.
You can get a live, free 1GB database for 30 days.
The SQL Azure Team blog may be of interest.