Slow SP with date parameters solved.

Question

Post reply

Slow SP with date parameters solved.

Virgilio Licovali Bustos Ramirez

SSC Rookie

Points: 25
More actions
April 27, 2010 at 7:39 am

#386798

Comments posted to this topic are about the item Slow SP with date parameters solved.

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

ahaliav SSC Rookie Points: 26 More actions · Answer 1

ahaliav

SSC Rookie

Points: 26

April 28, 2010 at 12:46 am

#1158659

.

r5d4 SSCrazy Points: 2522 More actions · Answer 2

I don't understand the problem you are trying to solve.

Is it a parameterization issue?

Ditto previous comment i.e what sql version have you found this to be an issue on?

How large were your tables? Were they indexed? Did you look at the execution plan to analyse what was going on?

ahaliav SSC Rookie Points: 26 More actions · Answer 3

I checked it on 1030484 rows and in my case it worked the same when I run it from direct query and from a SP

Carlo Romagnano SSC-Insane Points: 22680 More actions · Answer 4

Starting from sql2000 sp4 and sql2005, sql2008, the optimizer changed strategy to retrieve data when you specify parameters in the where clause. So, in this case "column1 between @from and @to" for the optimizer means "read all rows" and starts with a full scan table instead of using index. Another solution is using hints and force the use of index:

select * from tab with(index(idx_tab)) where column1 between @from and @to

hillsl SSC Eights! Points: 866 More actions · Answer 5

Not very scientific, but I found that the first time I ran, the result from the @tableparams was considerably faster when selecting approx 17,000 rows from 682,000, where there is no useful index.

(17234 row(s) affected)

SQL Server Execution Times:

CPU time = 2250 ms, elapsed time = 8095 ms.

-- this one was parameterised

(17234 row(s) affected)

SQL Server Execution Times:

CPU time = 515 ms, elapsed time = 1784 ms.

-- this using the table variable

Running exactly the same thing a second time the difference was greatly reduced.

(17234 row(s) affected)

SQL Server Execution Times:

CPU time = 343 ms, elapsed time = 958 ms.

(17234 row(s) affected)

SQL Server Execution Times:

CPU time = 314 ms, elapsed time = 264 ms.

Using a different table, the paraemterised query was quicker on the second run.

christopher.gray Old Hand Points: 372 More actions · Answer 6

I've run across this problem several times as well.

I try copying the parameters into local variables, then use the local variables in the WHERE clause.

That almost always fixes the problem.

The two result in very different execution plans, though I've never really understood why.

I'd love to hear what is going on behind the scenes.

arussell_10 SSCrazy Points: 2110 More actions · Answer 7

It might be parameter sniffing. If you do what Christopher suggested this will resolve the issue with parameter sniffing. I think there are other ways to resolve the issue as well, but don't recall them right now. Just google parameter sniffing.

christopher.gray Old Hand Points: 372 More actions · Answer 8

On the subject of parameter sniffing, here's a good article that describes how that works (and best of all, how it can go wrong!)

http://www.sqlpointers.com/2006/11/parameter-sniffing-stored-procedures.html

brandonregister Grasshopper Points: 19 More actions · Answer 9

I had this same problem. I simply copied the code in the SPROC and then dropped the object. Lastly, I recreated the SPROC and everything ran fine.

akljfhnlaflkj SSC Guru Points: 76202 More actions · Answer 10

akljfhnlaflkj

SSC Guru

Points: 76202

May 19, 2016 at 7:13 am

#1880226

Thanks for the script.