Posted by Erland Sommarskog on 05/01/07 11:45

BillCo (coleman.bill@gmail.com) writes:
> Anyway, I figured it out in the end - here's the final result. Please
> feel free to tear it apart critically - I'm here to learn :)
>...
> WHERE (@strUnitID IS NULL OR tblUnits.strUnitID LIKE
> @strUnitID)
> AND (@strProjectName IS NULL OR tblProjects.strProjectName LIKE
> @strProjectName)
> ...

While this will work, beware that it will scan the tables every time,
and never use an index. If the data size is modest, this may not be
an issue, but if there are several million rows, it will not be that fun.



--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: Optional Where Parameters on Null Data
• Prev in forum: Re: Transform/transfer 50Gb - how to do it fast?
• Thread view: Re: Optional Where Parameters on Null Data

[Reply to this message]