CODEWITHSUNDEEP
sql-serverperformancestored-procedures
coding4fun
coding4fun

Reputation: 8219

How to troubleshoot sql server performance problem

Ok this general problem has reared its ugly head twice in the past 6 months (different stored procedure). We have our internal users report a timeout error in the application. We can reproduce the problem in the application in a controlled environment. So we go through the normal steps of checking for blocking using sp_who2. Everything looks good with no blocking. So we do a sql trace to see exactly how the procedure is being executed. We copy that to a new window in SQL Management Studio and execute what sql trace was telling us ADO.Net was doing it and it finished in milliseconds. Our applications timeout is 30 seconds. When this problem happened a couple months back we had SQL Server 2005. We now have upgraded to SQL Server 2008 R2. Whats the next step to diagnose a problem like this?

@Martin: Thanks for the response. I will read your post in detail and let you know what i found out. Until then here is the sql in the SP you requested:

Select 
    @Exists=0, 
    @EarnRecId=0,
    @SuppStatusId = 0,
    @SLRecId = 0,
    @EarnRecDS = Null

Select
    @EarnRecId = er.EarningsId,
    @EarnRecDS = Convert(Varchar(26),er.Datestamp, 109),
    @SuppStatusId = s.SuppStatusId,
    @SLRecId = s.SLId
From
    Tracking tr
    Inner Join Supps s On s.SuppId = tr.SuppId
    Inner Join Earnings er On er.EarnRecId = s.SuppId
Where
    tr.ClaimId = @ClaimId
    and er.FiscalYr = @FiscalYr
    And er.EmplyrId In (@EmpId1,@EmpId2)

If @EarnRecId > 0
    Begin
        Set @Exists=1
    End

Upvotes: 2

Views: 1765

Answers (2)

Alex from Jitbit
Alex from Jitbit

Reputation: 60952

Martin is totally right. But I'll add my 2 cents to summarize:

  1. Obviously, SSMS and your app use different execution plans
  2. Why? Because your app uses a cached plan and SSMS, by default, tells the server to always create a new plan.
  3. Fast and dirty solution - clear the cache

Run this

DBCC FREEPROCCACHE

Helps 90% of the time.

PS. (IMO) Say, you rebooted your server. The server is still busy starting things up etc, but your web app already starts getting http requests form users! So your poor little SQL starts creating and caching execution plans... While doing a ton of other things at the same time! That's why the execution plans are far from optimal after rebooting a busy machine...

Upvotes: 0

Martin Smith
Martin Smith

Reputation: 454020

Probably parameter sniffing.

When the stored procedure is invoked and there is no existing execution plan in the cache matching the set options for the connection a new execution plan will be compiled using the parameter values passed in on that invocation.

Sometimes this will happen when the parameters passed are atypical (e.g. have unusually high selectivity) so the generated plan will not be suitable for most other invocations with different parameters.

SSMS has a different default value for the option SET ARITH_ABORT so will not get handed the same problematic plan when you execute the stored procedure inside SSMS.

Next time it happens possibly the simplest way of investigating the issue would be to have 2 separate SSMS windows with the "Include Actual Execution Plan" option enabled and in one do

SET ARITHABORT OFF
EXEC YourProc ...

And in the other

SET ARITHABORT ON
EXEC YourProc ...

Assuming default ADO.NET and SSMS connection options the first one should use the bad plan from the cache.

If that doesn't work for you you could use profiler to see what other set options you need to fiddle with to get the bad plan or just use profiler to get the execution plans directly - or you can retrieve them from the DMVs as below.

select p.query_plan, *
from sys.dm_exec_requests r
cross apply sys.dm_exec_query_plan(r.plan_handle) p
where r.session_id = <spid of your ADO.NET connection>

You might find that the problematic plan is doing tens of thousands of individual index seeks for example whereas the good plan avoids this.

Upvotes: 4

Related Questions