> Is
> there a way in the where clause to define it so the where clause can take
> a
> parameter what ever its value and for the null not restrict the search.

"maa" <maa@discussions.microsoft.com> wrote in message
news:E40AA6CC-B1A3-4BF5-882E-9CF24997276E@microsoft.com...
>I have parameters to a stored procedure that may be null or have a value.
>In
> the case of a null value the search is not to be using that parameter. Is
> there a way in the where clause to define it so the where clause can take
> a
> parameter what ever its value and for the null not restrict the search.
> Company does not like dynamic SQL so that is not an option. Other option
> is
> copy and paste with different tests.
>
> Example:
>
> where( date=@DateTimeParameter )
>
> I have tried adding a boolean result but it is not being short circuited:
>
> where( 1=1 OR date=@DateTimeParameter )
>
> Thanks,
>
> Marc