SQL Server 2008可以每秒处理300个事务吗？ [英] Can SQL server 2008 handle 300 transactions a second?

问题描述

在我当前的项目中，数据库是SQL 2005，负载约为35个事务/秒。客户期望更多的业务，并计划每秒300个事务。当前，即使具有良好的基础结构，数据库也存在性能问题。一个典型的事务将至少具有一个更新/插入和几个选择。

In my current project, the DB is SQL 2005 and the load is around 35 transactions/second. The client is expecting more business and are planning for 300 transactions/second. Currently even with good infrastructure, DB is having performance issues. A typical transaction will have at least one update/insert and a couple of selects.

你们在处理过300 txn / s以上运行SQL的任何系统上工作过吗如果是2005年或2008年，那么您使用了哪种基础架构，交易的复杂程度如何？请分享您的经验。有人已经建议使用Teradata，我想知道是否确实需要这样做。

Have you guys worked on any systems that handled more than 300 txn/s running on SQL 2005 or 2008, if so what kind of infrastructure did you use how complex were the transactions? Please share your experience. Someone has already suggested using Teradata and I want to know if this is really needed or not. Not my job exactly, but curious about how much SQL can handle.

推荐答案

根据 tcp.org 对于SQL Server 2005，每秒可能会获得1,379个事务。 这是完成该系统的链接。 （该站点上有很多基于SQL Server的系统，它们的交易更多。我链接的只是我看过的第一个。）

According to tcp.org its possible for SQL Server 2005 to get 1,379 transactions per second. Here is a link to a system that's done it. (There are SQL Server based systems on that site that have far more transactions... the one I linked was just the first I one I looked at).

当然，如Kragen所言，这里的任何人都无法说是否能够实现这些结果。

Of course, as Kragen mentioned, whether you can achieve these results is impossible for anyone here to say.

这篇关于SQL Server 2008可以每秒处理300个事务吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！