June 20, 2008 at 1:08 pm
This performance counter ususally sits at 1 or 2 in our organization.
In a recent server crash incident, this number jumped to 30.
My questions are:
1. What is the exact meaning of this number? I understand that it measures batches/sec.
2. What is considerd high transactions database. What would this number be if a sever has high transactions.
3. Was there a DOS attack? Unfortunately, we don't have a profiler trace running at that time.
Could some one give me some pointers on how a DOS attack on SQL could occur that would raise this counter?
Thanks!:cool:
June 20, 2008 at 2:26 pm
The SQL Server General Statistics Transaction counter is not what you want to be using, as it does not track all transactions. Instead, use the SQLServer: SQL Statistics: Batch Requests/Sec counter, which more accurately reflects server activity.
While the SQLServer: SQL Statistics: Batch Requests/Sec counter can sometimes be useful, there are many more useful counters you can use to track performance. See http://www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx for more information.
You are not the subject of a DOS attack.
PurpleMist (6/20/2008)
This performance counter ususally sits at 1 or 2 in our organization.In a recent server crash incident, this number jumped to 30.
My questions are:
1. What is the exact meaning of this number? I understand that it measures batches/sec.
2. What is considerd high transactions database. What would this number be if a sever has high transactions.
3. Was there a DOS attack? Unfortunately, we don't have a profiler trace running at that time.
Could some one give me some pointers on how a DOS attack on SQL could occur that would raise this counter?
Thanks!:cool:
Brad M. McGehee
DBA
June 20, 2008 at 3:25 pm
Thanks for the recommendation.
Batches/Sec number is much higher than Transactions.
I just downoaded your ebooks by the way. Awesome work!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply