Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Profiler - Threshold values Expand / Collapse
Author
Message
Posted Friday, June 14, 2013 5:58 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 1, 2013 6:20 AM
Points: 3, Visits: 23
Hi,

I hope you pro's could help me out with some performance issues I'm having..
Oke, so we have some performance issues, I looked into some blogs of Brent Ozar regarding the use of Performance Monitor to do some monitoring, helped me out a lot. Next what I wanted to do was use SQL Profiler to see what was going on. I know how to use profiler and understand all the terminology, but.... what are the threshold values for the data columns like CPU, reads, writes etc. I know that the duration depends on what the business considers slow. But have no idea at what I am looking for when checking the rest of the data values....What is considered bad and good?
I've searched every where, but can't find the answer for my question... If someone could help me or give me some pointers I would be really thankfull.

Cheers SQL D.
Post #1463497
Posted Friday, June 14, 2013 6:00 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 1:01 AM
Points: 1,375, Visits: 2,660
I don't think there is a good or bad. It depends on your queries.

This is why creating benchmarks is so important. Then you have something to compare your profiler results to.
Post #1463499
Posted Friday, June 14, 2013 6:07 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 1, 2013 6:20 AM
Points: 3, Visits: 23
Thanks for the fast reply. So what you're saying basically is monitoring and tracing when performance is ok, then comparing with the trace when it's not performing as it should?

Post #1463503
Posted Friday, June 14, 2013 6:12 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 1:01 AM
Points: 1,375, Visits: 2,660
Yes - More or less.

Have a look here, might help you

https://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/
Post #1463509
Posted Friday, June 14, 2013 6:14 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:54 PM
Points: 42,434, Visits: 35,488
There's no magic threshold where below that it's fine and above that it's bad. There's only normal for your system and abnormal for your system.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1463511
Posted Friday, June 14, 2013 6:22 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 1, 2013 6:20 AM
Points: 3, Visits: 23
Oke, i'm reading the article part 1 and 2, after I'm done I'll continue my Q : )

But then my next Q; What is considered normal and abnormal?
What do you look for when using profiler? Which data columns e.g. shows you ... oke wait something is bad there..?

I know that duration is for queries that are for e.g. running slow or finding deadlocks and locks etc, i know all about that... but the rest....pfff... I think I'm starting to loose it ...
Post #1463518
Posted Friday, June 14, 2013 6:25 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 1:01 AM
Points: 1,375, Visits: 2,660
If you have a query that takes 10 hours to execute, that doesn't necessarily mean that it's slow - It could be normal for your system.
There is no set in stone threshold for what's good and what's bad - It depends on your system, you need to know what is abnormal/normal for your system.

Read those articles, it will show you which columns to look out for.

Post #1463521
Posted Friday, June 14, 2013 6:30 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:54 PM
Points: 42,434, Visits: 35,488
sqldkay (6/14/2013)
But then my next Q; What is considered normal and abnormal?


Normal = normal for your system
Abnormal = not normal for your system.

If a query runs normally 2 minutes and is running 25 minutes today, that's abnormal.
If a query runs normally 2 minutes and is running 5 seconds today, that's also abnormal.

Right at this moment, I'm tuning a query that's running on average 50ms. I'm tuning it because it runs around 250000 times an hour and is normally under 10ms.

What do you look for when using profiler? Which data columns e.g. shows you ... oke wait something is bad there..?


By themselves, none of them.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1463524
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse