February 24, 2011 at 12:50 pm
We installed a new third party application on our development server and I'm trying to determine how many transactions a second are hitting the application database. I've tried both SQL Profiler and Performance Monitor to try to obtain this information. However, I'm not sure if my approach is correct (or if there is a better way to do this than using these tools).
Environment - SQL Server 2008 SP1 running on Windows 2008 R2
I started my journey using Performance Monitor which is REALLY different than the once in Windows 2003. I'm tracing the "Transaction/sec" counter in the "MSSQL$<instance>:Databases" group and selecting just the one database of interest. The graph that displays seems to give me the information I need - avg, min, and max. But I can't figure-out how to store (save) the output as I want to run it for 24 hours.
So, I moved into SQL Profiler where I'm logging only the "SQLTransaction" event under "Transactions". When I summarize the data, grouping by hh:mm:ss (eliminating the milliseconds), the counts are much higher than Performance Monitor. There are a bunch of "sa" owned transactions that are "GhostCleanupTask". Don't know what this is but when I exclude those transactions, the Profiler counts are still higher than PerfMon.
I can only conclude I'm trying to compare apples and oranges. Can someone assist me as to whether either of these approaches are valid for determining how many transactions a second are being generated from the application? Or is there a better way?
Thanks,
Cindy
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy