July 19, 2013 at 1:13 pm
Hi,
When I add the below line of code to my stored procedure, the performance becoems very poor. Is there any other way I can do i ?
AND CustNum = CASE WHEN ISNULL(@CustNum,0) = 0 THEN CustNum ELSE @CustNum END
Thanks,
PSB
July 19, 2013 at 1:21 pm
PSB (7/19/2013)
Hi,When I add the below line of code to my stored procedure, the performance becoems very poor. Is there any other way I can do i ?
AND CustNum = CASE WHEN ISNULL(@CustNum,0) = 0 THEN CustNum ELSE @CustNum END
Thanks,
PSB
There is always another way to do something. However, from what you posted I doubt anybody can give you much solid advice. All we have is a portion of what appears to be a where clause. This has the appearance of a catch all type query.
Check out this article that explains the issue you are seeing here. http://sqlinthewild.co.za/index.php/2009/03/19/catch-all-queries/[/url]
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
July 20, 2013 at 3:58 am
the information that you have provided here is not that much and we cant able to give you proper solution...
please provide some more details...
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
July 20, 2013 at 4:42 pm
Still and considering the very common configuration of the WHERE clause the OP gave, the methods in the "Catch All Query" article that Sean posted will probably fit the bill.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply