This must have been so obvious to everyone else that nobody bothered to write an article on it... till now.

Situation
I have a report that returns room bookings based on a user and given a date range. The problem is that there are a few thousand users and Microsoft's SQL Server Reporting Services interface isn't the most fun to scroll endlessly down. Advanced users can type the name really fast for it to auto-scroll down to the desired name. Our advanced users are exceptions to the rule.

Problem
Consider the following query:

  1.  SELECT 
  2.       rb.[GivenDate] 
  3.       , rb.[DateStart] 
  4.       , rb.[DateFinish] 
  5.       , rb.[ContactUsername] 
  6.       , rb.[ContactName] 
  7.       , rb.[Room] 
  8.       , rb.[BookingNotes] 
  9.  FROM 
  10.       roombookings rb 
  11.  WHERE 
  12.      rb.[GivenDate] BETWEEN @GivenDate AND @ToDate 
  13.  AND 
  14.      rb.[ContactName] LIKE '%@GivenName%'   -- WARNING: 0 matching rows 
This returns nothing. Took me a while to figure why but it's the parameter that's the issue. You don't enclose it with apostrophes for one thing. So let me rewrite this:
  1.  SELECT 
  2.       rb.[GivenDate] 
  3.       , rb.[DateStart] 
  4.       , rb.[DateFinish] 
  5.       , rb.[ContactUsername] 
  6.       , rb.[ContactName] 
  7.       , rb.[Room] 
  8.       , rb.[BookingNotes] 
  9.  FROM 
  10.       roombookings rb 
  11.  WHERE 
  12.      rb.[GivenDate] BETWEEN @GivenDate AND @ToDate 
  13.  AND 
  14.      rb.[ContactName] LIKE '%'+@GivenName+'%'  --WORKS! Enclose percent signs as strings. 
For anyone that thinks there exists stupid questions, here's a silly answer which I hope helps!

Comments   

0 Rudolf Wednesday, 11th November 2015, 3:24 pm
Does this also work with blank or null values?
0 Trish M Thursday, 12th September 2013, 8:17 pm
Excellent tip. Thanks!

Add comment


Send