May 18, 2009 at 3:00 am
Hello,
How can i know which is the max of transaction by second? is it possible to know?
Thanks
May 18, 2009 at 4:40 am
I think the only way to do this is to use Profiler or run a trace against your system. But this will only give you a snapshot in time. It won't tell you overall.
SQL 2008 may have the tools to do this natively, but if you need to do it for 2005 and don't want to have traces running all the time (a wise decision, BTW), you may need to invest in third party monitoring tools like Imceda offers. I only mention Imceda because I know they have a tool. I think there might be other third party tools (Red Gate?), but I'm unsure of those company names.
May 18, 2009 at 8:07 am
Hi again,
Thanks for the answer, but I think i didnt explain very well, second try :), what i wish to know is if i can know what is the max of transactions that sql allows, by seconds.. or if there is a way to find out ?
Thanks again
May 18, 2009 at 8:32 am
There's no good answer to that. It depends on your hardware, your server configuration, and how much parallell threading you allow the server to do.
If you absolutely need a number, call Microsoft. But I doubt they'll give you one. It's dependant on too many factors to be a hard and fast rule.
May 18, 2009 at 8:56 am
http://www.tpc.org has various database benchmarks for OLTP and Data warehousing.
TPC-C simulates a complete computing environment where a population of users executes transactions against a database. The benchmark is centered around the principal activities (transactions) of an order-entry environment. These transactions include entering and delivering orders, recording payments, checking the status of orders, and monitoring the level of stock at the warehouses.
For TPC-C, SQL Server highest result was 1,200,000 transactions per second running on hardware that cost about $6 million.
Full details are available at http://www.tpc.org.
SQL = Scarcely Qualifies as a Language
May 18, 2009 at 10:20 am
If you're looking to load test a server you can run SQLIOSim. This microsoft tool will allow you to see just how much a server can handle. Obviously you don't want to run it on your production server. Rather, run it on a server to validate it for production as part of your burn-in process. This way you can validate the hardware and O/S, and establish a nice baseline to measure by.
May 18, 2009 at 11:23 am
As far as I know there is no set limit on number of transactions a SQL Server allows. It depends on how powerful SQL Server setup is, which depends on hardware resources at its desposal. You might have to create a becnchmark test, and run against your server to see how it fairs.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply