Can SQL server 2008 handle 300 transactions a second?

Faiz picture Faiz · Oct 22, 2009 · Viewed 10.5k times · Source

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.

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.

Answer

Justin picture Justin · Oct 22, 2009

Its impossible to tell without performance testing - it depends too much on your environment (the data in your tables, your hardware, the queries being run).