Optimizing Stored Procedure with Datetime parameter

[paulmac106]

Hi,

When I pass a date time parameter the stored procedure takes about 45
seconds, when I hard code the parameter it returns in 1 second. How can
I rewrite my stored procedure?

@createddatelower datetime

WHERE dbo.tblCaseHistory.eventdate > dateadd(d,-7,@createddatelower )
AND dbo.tblCaseHistory.eventdate < dateadd(d,-6,@createddatelower ) (45
seconds)

vs.

WHERE dbo.tblCaseHistory.eventdate > dateadd(d,-7,'11/15/05') AND
dbo.tblCaseHistory.eventdate < dateadd(d,-6,'11/15/05') (1 second)

thanks for your help,
Paul

[ZeldorBlat]

Do you get the same (correct) result with both queries?

[paulmac106]

Yes, the result is the same

[paulmac106]

I've read that perhaps the sp is not using the index. The table i'm
searching is a joined table in the sp...Do you know how i can force it
to use the index? Then name of the index is IndexDate

thanks,
Paul

[ZeldorBlat]

>Do you know how i can force it to use the index?

Check out "forceplan" as in:

set forceplan on

[Gert-Jan Strik]

Paul,

Your stored procedure could benefit from parameter sniffing if you
change the local variable into a parameter, as in:

CREATE PROCEDURE MyProcedure (@createddatelower datetime) AS
...
WHERE eventdate > dateadd(day,-7,@createddatelower)
...

EXEC MyProcedure '20051115'

HTH,
Gert-Jan

paulmac106 wrote:

Hi,

When I pass a date time parameter the stored procedure takes about 45
seconds, when I hard code the parameter it returns in 1 second. How can
I rewrite my stored procedure?

@createddatelower datetime

WHERE dbo.tblCaseHistory.eventdate > dateadd(d,-7,@createddatelower )
AND dbo.tblCaseHistory.eventdate < dateadd(d,-6,@createddatelower ) (45
seconds)

vs.

WHERE dbo.tblCaseHistory.eventdate > dateadd(d,-7,'11/15/05') AND
dbo.tblCaseHistory.eventdate < dateadd(d,-6,'11/15/05') (1 second)

thanks for your help,
Paul