I got a report using ignite tool which stated that one of my stored procedure (on sql server 2008) is taking 40.2% of total sql execution time.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I got a report using ignite tool which stated that one of my stored procedure (on sql server 2008) is taking 40.2% of total sql execution time.
It is possible if the proc is called tens of thousand of times a day or if the proc is running for 16 hours with 30 nested cursors…take a look at how many times it was executed…you can also drill down per hour in ignite and take a look at IO