SQL Server 2008 R2 - 网络版 VS。标准
我需要为一个项目选择 SQL Server 2008 R2 版本，但我不知道哪个版本最适合。网站每月应有 200 万次展示/10 万个唯一用户。该网站的数据库非常紧凑，最多占用 50MB。大多数查询都是带有一些复杂连接的 SELECT，但没有 UPDATE/DELETE/INSERT。
我认为网络版应该可以完成这项工作，但恐怕它不可升级或无法处理负载。你会推荐什么？
I need to choose a SQL Server 2008 R2 edition for a project but I don't know what edition suits best. Website should have 2M impressions/100K unique users each month. DB of the site is very compact and takes 50MB top. Most of the queries are SELECTs with some complicated joins, but no UPDATE/DELETE/INSERT.
I think the web edition should do the work, however I'm afraid it's not upgradeable or won't be able to handle the load. What would you recommend?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您是否考虑过使用 SQL Server Express？您的所有数据都将适合内存，并且由于它是只读的，因此您不会遇到太多锁争用问题，因此即使仅限于一个 CPU 也可能不会那么糟糕。
另外，考虑到您似乎还没有达到 2M 印象规模，为什么不从免费但功能齐全的选项开始，直到您真正需要更强大的选项（只要确保监控、计划、并相应地进行预算！）。
进行负载测试和运行模拟可以帮助指导您的决策。作为此过程的一部分，调整您的查询和索引 - 精心调整的 SQL Express 实例可以轻松胜过在任何其他版本中运行的实施不佳的系统。
Have you considered using SQL Server Express? All of your data is going to fit in memory and since it is read-only you're not going to have much issues with lock contention, so even being limited to one CPU may not be so bad.
Also, given that it sounds like you're not at the 2M impression scale yet, why not start with the free, yet fully capable, option until time comes when you really need a more powerful option (just be sure to monitor, plan, and budget accordingly!).
Doing load testing and running simulations can help guide your decision. Tune your queries and indexes as part of this - a finely tuned SQL Express instance can easily outperform a poorly implemented system running in the any of the other editions.
如果没有硬性数字来计算选项和/或实际负载测试，很难说，但我怀疑网络现在已经足够好了。无论哪种情况，如果规模不起作用，撤销都不是一个棘手的决定——你的代码库不会关心。
从规模上看，4 个处理器和最大内存还有很大的空间，特别是如果您的数据只有 50mb。你可以毫不费力地在 RAM 驱动器中运行它，这会让事情变得非常快。
Hard to tell without hard numbers to calculate out options and/or actual load tests, but I suspect web will do you good enough for now. In either case, it is not a tricky decision to undo if the scale does not work -- your codebase won't care.
Scale-wise, 4 processors and max memory is alot of room to go, especialy if your data is only 50mb. You could run that in a RAM drive without breaking a sweat, and that would make things insanely fast.